[Bugme-new] [Bug 4403] New: atomic counter underflow in smbfs

[bugme-daemon at osdl.org]

http://bugme.osdl.org/show_bug.cgi?id=4403

           Summary: atomic counter underflow in smbfs
    Kernel Version: 2.6.12-rc1-mm3
            Status: NEW
          Severity: high
             Owner: akpm at digeo.com
         Submitter: khali at linux-fr.org


Distribution: Slackware 9.1
Problem Description:

File operations on smbfs fail frequently with the following traces in dmesg:

smb_proc_readX_data: offset is larger than SMB_READX_MAX_PAD or negative!
smb_proc_readX_data: -35 > 64 || -35 < 0
smb_add_request: request [e1b2ce60, mid=400] timed out!
BUG: atomic counter underflow at:
 [<e9aa9df0>] smb_rput+0x50/0x60 [smbfs]
 [<e9aa3a3c>] smb_proc_readX+0xdc/0xf0 [smbfs]
 [<e9aa8d77>] smb_readpage_sync+0x97/0x120 [smbfs]
 [<e9aa8e17>] smb_readpage+0x17/0x60 [smbfs]
 [<c0134b80>] read_pages+0xf0/0x140
 [<c0134c7e>] __do_page_cache_readahead+0xae/0x100
 [<c0134e11>] blockable_page_cache_readahead+0x51/0xd0
 [<c0134f03>] make_ahead_window+0x73/0xb0
 [<c0134ff3>] page_cache_readahead+0xb3/0x170
 [<c012ed2c>] do_generic_mapping_read+0x53c/0x550
 [<e9aa52b0>] smb_proc_getattr_trans2+0x80/0xf0 [smbfs]
 [<c012efb7>] __generic_file_aio_read+0x1a7/0x1f0
 [<c012ed40>] file_read_actor+0x0/0xd0
 [<c012f10c>] generic_file_read+0x9c/0xc0
 [<c0124850>] autoremove_wake_function+0x0/0x50
 [<e9aa912e>] smb_file_read+0x7e/0x90 [smbfs]
 [<c0148114>] vfs_read+0xb4/0x140
 [<c0148407>] sys_read+0x47/0x80
 [<c0102975>] syscall_call+0x7/0xb

Even just listing smbfs mount points will cause trouble:
BUG: atomic counter underflow at:
 [<e9aa9df0>] smb_rput+0x50/0x60 [smbfs]
 [<e9aa5516>] smb_proc_getattr_trans2_all+0xd6/0xf0 [smbfs]
 [<c01543c9>] follow_mount+0x59/0xb0
 [<e9aa5835>] smb_proc_getattr+0x35/0x60 [smbfs]
 [<e9aa80c3>] smb_refresh_inode+0x23/0x120 [smbfs]
 [<e9aa81f4>] smb_revalidate_inode+0x34/0x40 [smbfs]
 [<e9aa89e9>] smb_getattr+0x19/0x40 [smbfs]
 [<e9aa89d0>] smb_getattr+0x0/0x40 [smbfs]
 [<c015071a>] vfs_getattr+0x2a/0x90
 [<c0150810>] vfs_lstat+0x40/0x50
 [<c0150e52>] sys_lstat64+0x12/0x30
 [<c010db70>] do_page_fault+0x0/0x581
 [<c0102975>] syscall_call+0x7/0xb

If it matters, the local SMB client is samba 2.2.10, and the remote SMB server
is samba 2.2.10 as well.

Steps to reproduce:
cat /mnt/some_smbfs/some_file > /dev/null
or
ls -l /mnt (where some mount points have smbfs type)

Grep'ing through the logs reveals that the problem never happened before this
morning so the problem has to be new in 2.6.12-rc1-mm3

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.