Hide Forgot
Description of problem: When using s3ql (an Amazon AWS S3 filesystem which uses fuse), it warns with "BUG: sleeping function called from invalid context at mm/slub.c:1701" Version-Release number of selected component (if applicable): kernel-2.6.35.10-77.fc14.x86_64 How reproducible: Often Steps to Reproduce: 1. Mount s3ql filesystem 2. Use as normal 3. Unmount Actual results: Works, but kernel warnings Expected results: Nothing from kernel Additional info: The same fuse filesystem running on 2.6.32.26-175.fc12.i686.PAE has no problems. The full warning is: [ 4108.811981] BUG: sleeping function called from invalid context at mm/slub.c:1701 [ 4108.811985] in_atomic(): 1, irqs_disabled(): 0, pid: 14860, name: mount.s3ql [ 4108.811988] Pid: 14860, comm: mount.s3ql Not tainted 2.6.35.10-77.fc14.x86_64 #1 [ 4108.811990] Call Trace: [ 4108.811998] [<ffffffff8103d22d>] __might_sleep+0xeb/0xf0 [ 4108.812032] [<ffffffff811096e6>] kmem_cache_alloc_notrace+0x3d/0xb1 [ 4108.812039] [<ffffffffa05d2a5e>] fuse_dev_do_write+0x152/0x4e6 [fuse] [ 4108.812044] [<ffffffffa05d2670>] ? fuse_dev_do_read.clone.11+0x396/0x40b [fuse] [ 4108.812049] [<ffffffffa05d300f>] ? fuse_dev_write+0x0/0x62 [fuse] [ 4108.812053] [<ffffffffa05d306f>] fuse_dev_write+0x60/0x62 [fuse] [ 4108.812058] [<ffffffff811176aa>] do_sync_readv_writev+0xc1/0x100 [ 4108.812062] [<ffffffff8103c142>] ? need_resched+0x23/0x2d [ 4108.812065] [<ffffffff8103c15a>] ? should_resched+0xe/0x2e [ 4108.812069] [<ffffffff811e3bfa>] ? selinux_file_permission+0x5a/0xb9 [ 4108.812074] [<ffffffff811dc621>] ? security_file_permission+0x16/0x18 [ 4108.812077] [<ffffffff81117900>] do_readv_writev+0xa7/0x127 [ 4108.812080] [<ffffffff81116a5e>] ? fsnotify_access+0x6c/0x74 [ 4108.812084] [<ffffffff811182c9>] ? fput+0x22/0x1ed [ 4108.812087] [<ffffffff811179c5>] vfs_writev+0x45/0x47 [ 4108.812090] [<ffffffff81117ae8>] sys_writev+0x4a/0x93 [ 4108.812094] [<ffffffff81009cf2>] system_call_fastpath+0x16/0x1b
It appears to be here in fuse_notify_inval_entry(): buf = kzalloc(FUSE_NAME_MAX + 1, GFP_KERNEL); Called from fuse_dev_do_write(): /* * Zero oh.unique indicates unsolicited notification message * and error contains notification code. */ if (!oh.unique) { err = fuse_notify(fc, oh.error, nbytes - sizeof(oh), cs); return err ? err : nbytes; } I can't see what is causing in_atomic() to be true there, though.
Does this still happen on the latest f14 or f15 kernel?
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping