[linux-cifs-client] possible bug in Linux CIFS client code bundled with kernel 2.6.14

[studdugie]

Hello. I'm using the CIFS client included with  the 2.6.14 linux
kernel on the AMD64 Opteron processor. Every few weeks the CIFS client
crashes with the following message (from dmesg):
Unable to handle kernel paging request at 0000387294fa11c4 RIP:
<ffffffff8020e3c5>{small_smb_init+53}
PGD 0
Oops: 0000 [1] SMP
CPU 0
Modules linked in:
Pid: 167, comm: cifsoplockd Tainted: G   M  2.6.14 #1
RIP: 0010:[<ffffffff8020e3c5>] <ffffffff8020e3c5>{small_smb_init+53}
RSP: 0000:ffff81007feabe08  EFLAGS: 00010202
RAX: 0000000000000002 RBX: ffff8102ff5fea00 RCX: ffff81007feabed8
RDX: 0000387294fa1180 RSI: 0000000000000008 RDI: 0000000000000024
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000024 R14: 0000000000000000 R15: 0000000000000000
FS:  00000000402bd960(0000) GS:ffffffff80563800(0000) knlGS:0000000000000000
CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000387294fa11c4 CR3: 000000014dde0000 CR4: 00000000000006e0
Process cifsoplockd (pid: 167, threadinfo ffff81007feaa000, task
ffff81007fea9620)
Stack: ffff81007feabed8 0000000880156b0b ffff81007feabe58 0000000000000000
       ffff8102ff5fea00 ffffffffffffffff ffff81022934de50 ffffffff80162707
       0000000000000000 ffffffff80162bf3
Call Trace:<ffffffff80162707>{pagevec_lookup+23}
<ffffffff80162bf3>{invalidate_mapping_pages+211}
       <ffffffff8020fb07>{CIFSSMBLock+151}
<ffffffff8020e2f9>{cifs_oplock_thread+441}
       <ffffffff8010ea9e>{child_rip+8} <ffffffff8020e140>{cifs_oplock_thread+0}
       <ffffffff8010ea96>{child_rip+0}

Code: 83 7a 44 02 0f 84 21 02 00 00 48 8b 42 38 48 85 c0 0f 84 14
RIP <ffffffff8020e3c5>{small_smb_init+53} RSP <ffff81007feabe08>
CR2: 0000387294fa11c4
 <6>Machine check events logged
general protection fault: 0000 [2] SMP
CPU 0
Modules linked in:
Pid: 20266, comm: cifsd Tainted: G   M  2.6.14 #1
RIP: 0010:[<ffffffff8012ce39>] <ffffffff8012ce39>{try_to_wake_up+57}
RSP: 0018:ffff81024e399dd8  EFLAGS: 00010096
RAX: 33322e3631322f2f RBX: ffff8102ce5af980 RCX: 000000000000000f
RDX: 0000000000000000 RSI: 000000000000000f RDI: ffff81007fea9620
RBP: ffff81024e399e38 R08: ffff81007fe20a50 R09: ffff81007fe20a60
R10: 00000000000a757c R11: 0000000000000000 R12: ffffffff805a3640
R13: ffff81007fea9620 R14: ffff8102ce5af980 R15: 000000000000000f
FS:  00002aaaaade6ae0(0000) GS:ffffffff80563800(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00002aab5f4ce000 CR3: 000000022e1f5000 CR4: 00000000000006e0
Process cifsd (pid: 20266, threadinfo ffff81024e398000, task ffff8102f65b8960)
Stack: ffff8102fe4ca200 ffff810143fadd30 0000000000008009 0000000000000000
       0000000086e0d980 0000000000000292 0000000000000296 ffff8102ce5af980
       ffff81007ffb9840 ffff8102ce5af980
Call Trace:<ffffffff80221539>{is_valid_oplock_break+521}
<ffffffff802168ae>{cifs_demultiplex_thread+2158}
       <ffffffff8010ea9e>{child_rip+8}
<ffffffff80216040>{cifs_demultiplex_thread+0}
       <ffffffff8010ea96>{child_rip+0}

Code: 8b 40 18 48 c1 e0 07 48 8b 98 08 38 56 80 4c 01 e3 48 89 df
RIP <ffffffff8012ce39>{try_to_wake_up+57} RSP <ffff81024e399dd8>
The share to which the error refers is a Windows 2003 (SP1) box. 
Unfortunately, I'm unable to reproduce the error at will, but I hope
what I've posted can still be benefical.

I'm  not expecting a "fix" or anything like that but I would certainly
appreciate if someone could fill me in as to what side of the
communications channel is responsible for the error, CIFS or Windows.

Thanx,

Dane