On Thu, 6 Jan 2011, Andrew Morton wrote:
> mysterious.

commit 7909b1c6 (fuse: don't use atomic kmap) should fix this.

CC-d [email protected].  Greg, could you please add this commit to the
stable tree?

Thanks,
Miklos

> 
> Begin forwarded message:
> 
> Date: Fri, 7 Jan 2011 00:52:48 GMT
> From: [email protected]
> To: [email protected]
> Subject: [Bugme-new] [Bug 26272] New: BUG: Scheduling while atomic in 
> fuse_notify_inval_entry
> 
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=26272
> 
>            Summary: BUG: Scheduling while atomic in
>                     fuse_notify_inval_entry
>            Product: File System
>            Version: 2.5
>     Kernel Version: 2.6.35-23-generic
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Other
>         AssignedTo: [email protected]
>         ReportedBy: [email protected]
>         Regression: No
> 
> 
> Am I right in blaming FUSE for this?
> 
>  BUG: scheduling while atomic: python/6728/0x10000001
>  Modules linked in: ip6table_filter ip6_tables binfmt_misc vmnet vmblock vsock
> vmci vmmon ipt_M
>  Pid: 6728, comm: python Not tainted 2.6.35-23-generic #41-Ubuntu
>  Call Trace:
>   [<c013eb32>] __schedule_bug+0x62/0x70
>   [<c05c7700>] schedule+0x760/0x7a0
>   [<c05c94ef>] ? _raw_spin_lock_irqsave+0x2f/0x50
>   [<c01316e0>] ? gup_pte_range+0x100/0x170
>   [<c05c7882>] _cond_resched+0x32/0x50
>   [<c020c828>] kmem_cache_alloc_notrace+0x78/0xb0
>   [<c0131795>] ? gup_pud_range+0x45/0x80
>   [<c02ea58a>] ? fuse_notify_inval_entry+0x2a/0x1b0
>   [<c02ea58a>] fuse_notify_inval_entry+0x2a/0x1b0
>   [<f83b47fd>] ? i915_driver_irq_handler+0x21d/0x490 [i915]
>   [<c02e872c>] ? fuse_copy_do+0x3c/0x70
>   [<c02ea78b>] fuse_notify+0x7b/0xc0
>   [<c02e8a7d>] ? fuse_copy_one+0x3d/0x50
>   [<c02ea8cc>] fuse_dev_do_write+0xfc/0x320
>   [...]
> 
> 
> This is not reproducible at will, but happens several times a day. The
> fuse_notify_inval_entr is always near the top of the call stack.
> 
> -- 
> Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
> 

_______________________________________________
stable mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/stable

Reply via email to