2.6.7 Samba OOPS (in smb_readdir)

[Brice Goglin]

Hi Linus,

I am using Samba on my Compaq Evo N600c with an uptodate Debian
Testing and a 2.6.7 (.config attached).

When listing a samba mount point just after mounting it, 
I get this oops. I don't know why nautilus is used here, I
just called 'ls'.

I get the same oops with 2.6.7-rc3 (can't try previous releases).

Regards.

Brice Goglin



smb_lookup: find //.Trash-bgoglin failed, error=-5
Unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:
00000000
*pde = 00000000
Oops: 0000 [#1]
PREEMPT 
Modules linked in: dm_mod
CPU:    0
EIP:    0060:[<00000000>]    Not tainted
EFLAGS: 00010246   (2.6.7) 
EIP is at 0x0
eax: dfc21ccc   ebx: e160cf30   ecx: c01684c0   edx: e7fa4bd8
esi: e160cfa0   edi: c13f0780   ebp: df839740   esp: e160cefc
ds: 007b   es: 007b   ss: 0068
Process nautilus (pid: 2649, threadinfo=e160c000 task=e101f3d0)
Stack: c01f1536 df839740 e160cfa0 c01684c0 e160cf30 00000000 00000002 00000004 
       df7faeb0 00000000 df83c000 e7fa4bd8 df8acbe0 00000000 fffd18ab 00000000 
       00000000 00000000 df83c000 00000002 00000000 00000000 00000001 00000004 
Call Trace:
[<c01f1536>] smb_readdir+0x3e6/0x580
[<c01684c0>] filldir64+0x0/0x100
[<c01681b9>] vfs_readdir+0x89/0xa0
[<c01684c0>] filldir64+0x0/0x100
[<c016862e>] sys_getdents64+0x6e/0xaa
[<c01684c0>] filldir64+0x0/0x100
[<c010510b>] syscall_call+0x7/0xb
       
  Code:  Bad EIP value.
       


On 16/06/2004-08:00, Linus Torvalds wrote:

> 
> Ok, it's out there. The most notable change may be the one-liner that 
> should fix the embarrassing FP exception problem. Other than that, we've 
> had a random collection of fixes and updates since rc3. cifs, ntfs, 
> cpufreq. ide, sparc, s390.
> 
> Full 2.6.6->2.6.7 changelog available at the same places the release is.
> 
> 		Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/