[GH-ISSUE #25] s3fs appears to crash on ls with permission failure #17

New issue

Closed

opened 2026-03-04 01:41:12 +03:00 by kerem · 4 comments

kerem commented

2026-03-04 01:41:12 +03:00

Owner

Originally created by @rpattcorner on GitHub (Mar 23, 2014).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/25

Use case:

S3fs latest as of 3/23/14, e.g. 1.74
Arrange s3 bucket and iam role permissions for account a to write account b bucket (we wrote to a top level pseudo-folder, e.g. "files/whatever"
Copy files from a to b with a 'brute force' tool like aws cli (sync or copy)
Observe that the ACL on account b does not have account b owner rights ACL (because account a wrote the file)

Now ...
List the top level bucket with s3fs and see s3fs is working
List the top level folder and observe the segfault
Mar 23 11:44:52 ip-10-0-0-62 kernel: s3fs[23263]: segfault at 0 ip 0000000000423639 sp 00007f9a1ee22760 error 4 in s3fs[400000+51000]

Thing is ... s3fs will segfault if any file in a listing fails permissions in this way.
Suggested fix:

Catch and trap any ACL error
Print out message object: XXXX cannot be (whatever the operation was)
Continue to next operation

Originally created by @rpattcorner on GitHub (Mar 23, 2014). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/25 Use case: - S3fs latest as of 3/23/14, e.g. 1.74 - Arrange s3 bucket and iam role permissions for account a to write account b bucket (we wrote to a top level pseudo-folder, e.g. "files/whatever" - Copy files from a to b with a 'brute force' tool like aws cli (sync or copy) - Observe that the ACL on account b does not have account b owner rights ACL (because account a wrote the file) Now ... List the top level bucket with s3fs and see s3fs is working List the top level folder and observe the segfault Mar 23 11:44:52 ip-10-0-0-62 kernel: s3fs[23263]: segfault at 0 ip 0000000000423639 sp 00007f9a1ee22760 error 4 in s3fs[400000+51000] Thing is ... s3fs will segfault if **any** file in a listing fails permissions in this way. Suggested fix: - Catch and trap any ACL error - Print out message object: XXXX cannot be (whatever the operation was) - Continue to next operation

kerem closed this issue

2026-03-04 01:41:12 +03:00

kerem commented

2026-03-04 01:41:13 +03:00

Author

Owner

@ggtakec commented on GitHub (Mar 29, 2014):

If you can, please run s3fs with "-d" option.
(if you run s3fs foreground, you can specify with "-f" option. It puts more information for debugging.)
And if you can, please try to use "bugfix#18" branch on s3fs-fuse.

@ggtakec commented on GitHub (Mar 29, 2014): If you can, please run s3fs with "-d" option. (if you run s3fs foreground, you can specify with "-f" option. It puts more information for debugging.) And if you can, please try to use "bugfix#18" branch on s3fs-fuse.

kerem commented

2026-03-04 01:41:13 +03:00

Author

Owner

@rpattcorner commented on GitHub (Mar 29, 2014):

Thank you. I’m in the midst of a production release so it may take a couple days. Any way to pass the –d through to the “mount”-oriented syntax.

I think you want us to rebuild using the bugfix#18 branch … is that production ready in your opinion?

Thank you for the response!

From: Takeshi Nakatani [mailto:notifications@github.com]
Sent: Saturday, March 29, 2014 11:13 AM
To: s3fs-fuse/s3fs-fuse
Cc: Robert Patt-Corner
Subject: Re: [s3fs-fuse] s3fs appears to crash on ls with permission failure (#25)

—
Reply to this email directly or view it on GitHubhttps://github.com/s3fs-fuse/s3fs-fuse/issues/25#issuecomment-38998295.

@rpattcorner commented on GitHub (Mar 29, 2014): Thank you. I’m in the midst of a production release so it may take a couple days. Any way to pass the –d through to the “mount”-oriented syntax. I think you want us to rebuild using the bugfix#18 branch … is that production ready in your opinion? Thank you for the response! R. From: Takeshi Nakatani [mailto:notifications@github.com] Sent: Saturday, March 29, 2014 11:13 AM To: s3fs-fuse/s3fs-fuse Cc: Robert Patt-Corner Subject: Re: [s3fs-fuse] s3fs appears to crash on ls with permission failure (#25) If you can, please run s3fs with "-d" option. (if you run s3fs foreground, you can specify with "-f" option. It puts more information for debugging.) And if you can, please try to use "bugfix#18" branch on s3fs-fuse. — Reply to this email directly or view it on GitHubhttps://github.com/s3fs-fuse/s3fs-fuse/issues/25#issuecomment-38998295.

kerem commented

2026-03-04 01:41:13 +03:00

Author

Owner

@ggtakec commented on GitHub (Mar 29, 2014):

You need to run s3fs manually(command line) for specifying "-d" option.
And I think "bugfix#18" is good for use production.
It is not merged master branch yet, but it is only simple bug fixed.

@ggtakec commented on GitHub (Mar 29, 2014): You need to run s3fs manually(command line) for specifying "-d" option. And I think "bugfix#18" is good for use production. It is not merged master branch yet, but it is only simple bug fixed.

kerem commented

2026-03-04 01:41:13 +03:00

Author

Owner

@ggtakec commented on GitHub (Jan 17, 2016):

I'm sorry about this Issue had been left at a long period of time.

If you have this problem yet, please try to use latest code because some problem about multipart request etc were fixed.
("-f", "dbglevel" and "curldbg" options help to solve your problem.)
And if you found a problem, please post new issue.

Thanks in advance for your help.

@ggtakec commented on GitHub (Jan 17, 2016): I'm sorry about this Issue had been left at a long period of time. If you have this problem yet, please try to use latest code because some problem about multipart request etc were fixed. ("-f", "dbglevel" and "curldbg" options help to solve your problem.) And if you found a problem, please post new issue. Thanks in advance for your help.

kerem referenced this issue

2026-03-04 01:47:21 +03:00

[GH-ISSUE #1191] s3fs crash during cache read #630