linux-kernel - Re: 2.6.20.2: kernel BUG at fs/nfs/write.c:505!

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 12 Mar 2007 13:00:31 -0400
From:	Trond Myklebust <trond.myklebust@....uio.no>
To:	Stresslinux Kernel <lk@...esslinux.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.20.2: kernel BUG at fs/nfs/write.c:505!

On Mon, 2007-03-12 at 14:39 +0100, Stresslinux Kernel wrote:
> Hello List,
> 
> running the following command
> 
> /sbin/grub-install --root-directory=/mnt --no-floppy /dev/sda
> 
> from a nfsroot system with kernel 2.6.20.2 (x86_64) results in:
> 
> ------------[ cut here ]------------
> kernel BUG at fs/nfs/write.c:505!
> invalid opcode: 0000 [1] SMP
> CPU 0
> Modules linked in: ipv6 genrtc
> Pid: 1464, comm: grub-install Not tainted 2.6.20.2 #1
> RIP: 0010:[<ffffffff8032fb83>]  [<ffffffff8032fb83>] nfs_wait_on_requests_locked+0x43/0xb2
> RSP: 0018:ffff81007d669ca8  EFLAGS: 00010246
> RAX: 00000000fffff0ba RBX: 0000000000000000 RCX: ffffffff802917aa
> RDX: 0000000000000000 RSI: ffff81007d669cb0 RDI: ffff810002f5f9d8
> RBP: ffff810002f5f898 R08: 0000000000000001 R09: 0000000000000286
> R10: 7fffffffffffffff R11: 0000000000000286 R12: 74d83948d2310001
> R13: 0000000000000000 R14: ffffffffffffffff R15: 0000000000000000
> FS:  00002b24eb8214a0(0000) GS:ffffffff809d6000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 0000000000596d88 CR3: 000000007d594000 CR4: 00000000000006e0
> Process grub-install (pid: 1464, threadinfo ffff81007d668000, task ffff81007e885840)
> Stack:  ffff810002f5f898 ffffffff802917aa 0000000000000000 ffff810002f5fb58
>  0000000000000020 ffff810002f5f898 ffff81007d669da8 ffffffff80331245
>  000000000000002e ffff81007d669e48 0000000000000020 0000000000000000
> Call Trace:
>  [<ffffffff802917aa>] bd_forget+0x8d/0x8e
>  [<ffffffff80331245>] nfs_sync_mapping_wait+0xbe/0x1ec
>  [<ffffffff80331486>] nfs_sync_mapping_range+0x80/0xa1
>  [<ffffffff80328a1c>] nfs_getattr+0x2e/0x9b
>  [<ffffffff80272313>] vfs_getattr+0x1d/0x2b
>  [<ffffffff802723aa>] vfs_lstat_fd+0x2f/0x47
>  [<ffffffff8021c3ce>] do_page_fault+0x279/0x572
>  [<ffffffff80237c17>] do_sigaction+0x6b/0x1b0
>  [<ffffffff8027270a>] sys_newlstat+0x19/0x31
>  [<ffffffff807231ed>] error_exit+0x0/0x84
>  [<ffffffff80209dde>] system_call+0x7e/0x83
> 
> 
> Code: 0f 0b eb fe f0 ff 41 44 c7 85 18 01 00 00 01 00 00 00 48 8b
> RIP  [<ffffffff8032fb83>] nfs_wait_on_requests_locked+0x43/0xb2
>  RSP <ffff81007d669ca8>

Known issue. There is already a fix available in the -mm kernel
(attached).

Cheers
  Trond


View attachment "linux-2.6.20-001-fix_block_device_getattr.dif" of type "text/plain" (819 bytes)