From: Anton Starikov (ant.starikov_at_gmail_dot_com)
Date: Thu Feb 25 2010 - 15:30:36 PST
Here I forward reply from Jeff Layton @redhat about my bug report. He suggests that this can be and issue with BLCR module, see his comments in the middle of log. Anton. Begin forwarded message: > From: Jeff Layton <jlayton_at_redhat_dot_com> > Date: February 26, 2010 12:06:04 AM GMT+01:00 > To: Anton Starikov <ant.starikov_at_gmail_dot_com> > Cc: linux-nfs_at_vger_dot_kernel_dot_org > Subject: Re: NFS bug with 2.6.18-164.11.1.el5 kernel > > On Thu, 25 Feb 2010 23:35:27 +0100 > Anton Starikov <ant.starikov_at_gmail_dot_com> wrote: > >> >> ----------- 0d [user.notice] -----------: [cut here ] --------- [please bite here ] --------- >> Kernel 0d [user.notice] Kernel: BUG at fs/nfs/nfs4xdr.c:872 >> invalid 0d [user.notice] invalid: opcode: 0000 [1] >> SMP 0d [user.notice] SMP: >> Pid 0d [user.notice] Pid: 6821, comm: vasp Tainted: G 2.6.18-164.11.1.el5 #1 >> RIP 0d [user.notice] RIP: 0010:[<ffffffff881554ff>] >> 0d [user.notice] [<ffffffff881554ff>]: :nfs:encode_share_access+0x6d/0x82 >> RSP 0d [user.notice] RSP: 0018:ffff81041d0677b8 EFLAGS: 00010297 >> RAX 0d [user.notice] RAX: 00000000ffffffff RBX: ffff81041c0910a8 RCX: ffff81041c0910a8 >> RDX 0d [user.notice] RDX: 0000000000000008 RSI: 0000000000000008 RDI: ffff81041d067808 >> RBP 0d [user.notice] RBP: 0000000000000080 R08: ffff81041c09109c R09: 0000000000000009 >> R10 0d [user.notice] R10: ffff810415c9ce00 R11: ffffffff88158d4f R12: ffff81041d067808 >> R13 0d [user.notice] R13: ffff810417c4ea68 R14: ffff81041d067ab8 R15: ffff810426afa000 >> FS 0d [user.notice] FS: 00002b6e05f681c0(0000) GS:ffff81010e957240(0000) knlGS:0000000000000000 >> CS 0d [user.notice] CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b >> CR2 0d [user.notice] CR2: 0000003192a03080 CR3: 0000000417712000 CR4: 00000000000006e0 >> Process 0d [user.notice] Process: vasp (pid: 6821, threadinfo ffff81041d066000, task ffff81042689c100) >> Stack 0d [user.notice] Stack: >> ffffffffffffffff 0d [user.notice] ffffffffffffffff: >> ffff81041c0910a0 0d [user.notice] ffff81041c0910a0: >> ffff810426be2408 0d [user.notice] ffff810426be2408: >> ffffffff881589ff 0d [user.notice] ffffffff881589ff: >> 0d [user.notice] : >> 0000000000000000 0d [user.notice] 0000000000000000: >> ffff810417c4ea68 0d [user.notice] ffff810417c4ea68: >> ffff810426be2408 0d [user.notice] ffff810426be2408: >> ffffffff88158d4f 0d [user.notice] ffffffff88158d4f: >> 0d [user.notice] : >> ffff810417c4ea68 0d [user.notice] ffff810417c4ea68: >> ffffffff88158dbc 0d [user.notice] ffffffff88158dbc: >> ffff81041c0910b0 0d [user.notice] ffff81041c0910b0: >> ffff810417c4ea70 0d [user.notice] ffff810417c4ea70: >> 0d [user.notice] : >> Call 0d [user.notice] Call: Trace: >> 0d [user.notice] [<ffffffff881589ff>]: :nfs:encode_open+0x66/0x33e >> 0d [user.notice] [<ffffffff88158d4f>]: :ac+0x0/0xac >> 0d [user.notice] [<ffffffff88158dbc>]: :nfs:nfs4_xdr_enc_open+0x6d/0xac >> 0d [user.notice] [<ffffffff88158d4f>]: :nfs:nfs4_xdr_enc_open+0x0/0xac >> 0d [user.notice] [<ffffffff880313f0>]: :sunrpc:call_transmit+0x1bc/0x222 >> 0d [user.notice] [<ffffffff880369c1>]: :sunrpc:__rpc_execute+0x92/0x24e >> 0d [user.notice] [<ffffffff88036bd4>]: :sunrpc:rpc_run_task+0x37/0x3f >> 0d [user.notice] [<ffffffff881501b1>]: :nfs:_nfs4_proc_open+0x50/0x1aa >> 0d [user.notice] [<ffffffff881510c3>]: :nfs:nfs4_do_open+0xc2/0x1dd >> 0d [user.notice] [<ffffffff88152a89>]: :nfs:nfs4_proc_create+0x7f/0x1b2 >> 0d [user.notice] [<ffffffff8012827c>]: avc_has_perm+0x46/0x58 >> 0d [user.notice] [<ffffffff8813d18a>]: :nfs:nfs_create+0x91/0x103 >> 0d [user.notice] [<ffffffff8003a593>]: vfs_create+0xe6/0x158 >> 0d [user.notice] [<ffffffff887e5d16>]: :blcr:cr_mknod+0x19f/0x2b8 > > Hmmm...so this "blcr" module is calling down into vfs_create (I guess > to create a device or pipe or something?). If it's crashing in > encode_share_access then I suspect that the problem is that it's not > filling out the open_intent data in the nameidata that it's passing > down to vfs_create. > > IOW, this is likely a bug in the "blcr" module and not in RHEL. > >> 0d [user.notice] [<ffffffff887e5ee0>]: :blcr:cr_filp_mknod+0x30/0x12e >> 0d [user.notice] [<ffffffff887e629a>]: :blcr:cr_uread+0x40/0x91 >> 0d [user.notice] [<ffffffff887e6e20>]: :blcr:cr_mkunlinked+0x47/0x14d >> 0d [user.notice] [<ffffffff887eaea1>]: :blcr:cr_restore_open_file+0x195/0x332 >> 0d [user.notice] [<ffffffff887ec9d7>]: :blcr:cr_rstrt_child+0x1354/0x1de2 >> 0d [user.notice] [<ffffffff8008ac96>]: __wake_up_common+0x3e/0x68 >> 0d [user.notice] [<ffffffff8008c86c>]: default_wake_function+0x0/0xe >> 0d [user.notice] [<ffffffff800646f9>]: __down_failed+0x35/0x3a >> 0d [user.notice] [<ffffffff800421b6>]: do_ioctl+0x55/0x6b >> 0d [user.notice] [<ffffffff80030293>]: vfs_ioctl+0x457/0x4b9 >> 0d [user.notice] [<ffffffff8004c843>]: sys_ioctl+0x59/0x78 >> 0d [user.notice] [<ffffffff8005d28d>]: tracesys+0xd5/0xe0 > > -- > Jeff Layton <jlayton_at_redhat_dot_com>