linux-kernel - Re: [linux-cifs-client] Re: BUG: scheduling while atomic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <46D5A8F9.2010109@us.ibm.com>
Date:	Wed, 29 Aug 2007 12:12:25 -0500
From:	"Steve French (smfltc)" <smfltc@...ibm.com>
To:	Dave Kleikamp <shaggy@...ux.vnet.ibm.com>
CC:	Michael Deegan <michael@....gu.uwa.edu.au>,
	linux-cifs-client@...ts.samba.org, linux-kernel@...r.kernel.org
Subject: Re: [linux-cifs-client] Re: BUG: scheduling while atomic - linux
 2.6.22

Dave Kleikamp wrote:

>On Tue, 2007-08-28 at 07:11 +0800, Michael Deegan wrote:
>  
>
>>Hi,
>>
>>On Tue Aug 7 16:00:19 GMT 2007, Martin Koegler  wrote:
>>    
>>
>>>A vanilla 2.6.22 kernel (SMP PREEMPT i686) produced the following messages, while working with a CIFS mount point:
>>>      
>>>
>>Aug 27 22:33:08 wibble kernel: BUG: scheduling while atomic: bash/0x00000001/4077
>>Aug 27 22:33:08 wibble kernel:
>>Aug 27 22:33:08 wibble kernel: Call Trace:
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff805265df>] __sched_text_start+0x5f/0x79b
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff8049cb7a>] kernel_sendmsg+0x2c/0x3e
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff8032ba42>] wait_for_response+0xbe/0x155
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff802392bf>] autoremove_wake_function+0x0/0x2e
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff8032c0e1>] SendReceive+0x1fb/0x3f8
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff803192c2>] CIFSSMBOpen+0x1c6/0x27a
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff80323b8a>] cifs_reopen_file+0x1ea/0x356
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff8032455c>] find_writable_file+0x84/0xe7
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff80324b51>] is_size_safe_to_change+0x16/0x4e
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff8032fbc7>] fill_in_inode+0x270/0x4ec
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff80330c67>] cifs_readdir+0xe24/0x1071
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff802733c8>] filldir64+0x0/0xb8
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff80218c71>] do_page_fault+0x40b/0x74a
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff80527ffb>] __mutex_lock_slowpath+0x234/0x23f
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff802733c8>] filldir64+0x0/0xb8
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff80273594>] vfs_readdir+0x5d/0x92
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff8027363e>] sys_getdents64+0x75/0xba
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff8052948d>] error_exit+0x0/0x84
>>Aug 27 22:33:08 wibble kernel:  [<ffffffff8020958e>] system_call+0x7e/0x83
>>Aug 27 22:33:08 wibble kernel:
>>
>>I'm using a 2.6.22.1 kernel (with SMP and PREEMPT, including BKL) on Debian
>>etch AMD64, and Samba 3.0.24-6etch4.
>>    
>>
>
>This is a known problem that is fixed in 2.6.23-rc4.  cifs_readdir()
>takes a spinlock and calls a blocking function.  The fix is here:
>http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=a403a0a370946e7dbcda6464a3509089daee54bc
>
>Steve,
>Has this patch been submitted to the stable kernel?
>
>  
>
No - but seems like a resonable idea, although a little larger than 
typical patch to stable kernel.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/