From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, samba-technical@lists.samba.org,
nfs@lists.sourceforge.net, linuxppc-dev@ozlabs.org,
Andy Whitcroft <apw@shadowen.org>,
Balbir Singh <balbir@in.ibm.com>, Jan Kara <jack@suse.cz>
Subject: Re: [BUG] 2.6.24-rc3-mm2 kernel bug on nfs & cifs mounted partitions
Date: Thu, 29 Nov 2007 17:27:08 +0530 [thread overview]
Message-ID: <474EA914.1060502@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071129010906.772e0c15.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Thu, 29 Nov 2007 14:30:14 +0530 Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
>
>> Hi Andrew,
>>
>> While running file system stress on nfs and cifs mounted partitions, the machine
>> drops to xmon
>>
>> 1:mon> e
>> cpu 0x1: Vector: 300 (Data Access) at [c000000080a9f880]
>> pc: c0000000001392c8: .inotify_inode_queue_event+0x50/0x158
>> lr: c0000000001074d0: .vfs_link+0x204/0x298
>> sp: c000000080a9fb00
>> msr: 8000000000009032
>> dar: 280
>> dsisr: 40010000
>> current = 0xc0000000c8e6f670
>> paca = 0xc000000000512c00
>> pid = 2848, comm = fsstress
>> 1:mon> t
>> [c000000080a9fbd0] c0000000001074d0 .vfs_link+0x204/0x298
>> [c000000080a9fc70] c00000000010b6e0 .sys_linkat+0x134/0x1b4
>> [c000000080a9fe30] c00000000000872c syscall_exit+0x0/0x40
>> --- Exception: c00 (System Call) at 000000000ff1bdfc
>> SP (ffeaed10) is in userspace
>> 1:mon> r
>> R00 = c0000000001074d0 R16 = 0000000000000000
>> R01 = c000000080a9fb00 R17 = 0000000000000000
>> R02 = c00000000060c380 R18 = 0000000000000000
>> R03 = 0000000000000000 R19 = 0000000000000000
>> R04 = 0000000000000004 R20 = 0000000000000000
>> R05 = 0000000000000000 R21 = 0000000000000000
>> R06 = 0000000000000000 R22 = 0000000000000000
>> R07 = 0000000000000000 R23 = 0000000000000004
>> R08 = 0000000000000000 R24 = 0000000000000280
>> R09 = 0000000000000000 R25 = fffffffffffff000
>> R10 = 0000000000000001 R26 = c000000082827790
>> R11 = c0000000003963e8 R27 = c0000000828275a0
>> R12 = d000000000deec78 R28 = 0000000000000000
>> R13 = c000000000512c00 R29 = c00000007b18fcf0
>> R14 = 0000000000000000 R30 = c0000000005bc088
>> R15 = 0000000000000000 R31 = 0000000000000000
>> pc = c0000000001392c8 .inotify_inode_queue_event+0x50/0x158
>> lr = c0000000001074d0 .vfs_link+0x204/0x298
>> msr = 8000000000009032 cr = 24000882
>> ctr = c0000000003963e8 xer = 0000000000000000 trap = 300
>> dar = 0000000000000280 dsisr = 40010000
>>
>>
>> The gdb output shows
>>
>> 0xc0000000001076d4 is in vfs_symlink (include/linux/fsnotify.h:108).
>> 103 * fsnotify_create - 'name' was linked in
>> 104 */
>> 105 static inline void fsnotify_create(struct inode *inode, struct dentry *dentry)
>> 106 {
>> 107 inode_dir_notify(inode, DN_CREATE);
>> 108 inotify_inode_queue_event(inode, IN_CREATE, 0, dentry->d_name.name,
>> 109 dentry->d_inode);
>> 110 audit_inode_child(dentry->d_name.name, dentry, inode);
>> 111 }
>> 112
>>
>
> If it is reproducible can you please try reverting
> inotify-send-in_attrib-events-when-link-count-changes.patch?
Hi Andrew,
reverting the patch inotify-send-in_attrib-events-when-link-count-changes.patch, the
bug is not reproduced.
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
next prev parent reply other threads:[~2007-11-29 13:56 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 11:41 2.6.24-rc3-mm2 Andrew Morton
2007-11-28 12:40 ` 2.6.24-rc3-mm2 - Build Failure on powerpc timerfd() undeclared Kamalesh Babulal
2007-11-28 13:32 ` Arnd Bergmann
2007-11-28 18:43 ` Andrew Morton
2007-11-28 19:25 ` Davide Libenzi
2007-11-29 0:57 ` Arnd Bergmann
2007-11-28 13:07 ` 2.6.24-rc3-mm2 Build Failure at imacfb framebuffer driver Kamalesh Babulal
2007-11-28 18:51 ` Andrew Morton
2007-11-28 14:16 ` 2.6.24-rc3-mm2 Boaz Harrosh
2007-11-28 14:22 ` [PATCH] 2.6.24-rc3-mm2 build failure pasemi-rng driver Kamalesh Babulal
2007-12-01 19:32 ` Olof Johansson
2007-11-28 14:33 ` [BUG] 2.6.24-rc3-mm2 soft lockup while running tbench Kamalesh Babulal
2007-11-29 21:09 ` Andrew Morton
2007-11-30 5:09 ` Kamalesh Babulal
2007-11-28 19:52 ` 2.6.24-rc3-mm2 (build failure on s390) Christoph Lameter
2007-11-28 20:03 ` Andrew Morton
2007-11-28 19:54 ` 2.6.24-rc3-mm2 (build failure on arm) Christoph Lameter
2007-11-28 20:06 ` Andrew Morton
2007-11-28 20:33 ` Bartlomiej Zolnierkiewicz
2007-11-28 20:01 ` 2.6.24-rc3-mm2: Result: hostbyte=0x01 driverbyte=0x00\nend_request: I/O error Alexey Dobriyan
2007-11-28 21:40 ` Andrew Morton
2007-11-28 22:12 ` Alan Cox
2007-11-28 23:14 ` Matthew Wilcox
2007-11-28 23:36 ` Andrew Morton
2007-11-29 9:33 ` Boaz Harrosh
2007-11-28 22:05 ` 2.6.24-rc3-mm2 - *not* an insta-brick on my Latitude Valdis.Kletnieks
2007-11-28 23:06 ` named + capset = EPERM [Was: 2.6.24-rc3-mm2] Jiri Slaby
2007-11-28 23:31 ` Casey Schaufler
2007-11-28 23:47 ` Serge E. Hallyn
2007-11-29 0:04 ` Serge E. Hallyn
2007-11-29 0:17 ` Serge E. Hallyn
2007-11-29 22:56 ` Jiri Slaby
2007-11-29 3:23 ` 2.6.24-rc3-mm2 KAMEZAWA Hiroyuki
2007-11-29 5:24 ` 2.6.24-rc3-mm2 (bugfix for memory cgroup per-zone-struct allocation.) KAMEZAWA Hiroyuki
2007-11-29 21:25 ` Lee Schermerhorn
2007-11-30 0:14 ` KAMEZAWA Hiroyuki
2007-11-29 9:00 ` [BUG] 2.6.24-rc3-mm2 kernel bug on nfs & cifs mounted partitions Kamalesh Babulal
2007-11-29 9:09 ` Andrew Morton
2007-11-29 11:57 ` Kamalesh Babulal [this message]
2007-11-29 12:10 ` Jan Kara
2007-11-29 14:36 ` Kamalesh Babulal
2007-11-29 14:40 ` Jan Kara
2007-12-02 15:55 ` Kamalesh Babulal
2007-11-29 20:58 ` 2.6.24-rc3-mm2 Torsten Kaiser
2007-11-29 21:07 ` 2.6.24-rc3-mm2 Andrew Morton
2007-11-29 22:30 ` 2.6.24-rc3-mm2 Stefan Richter
2007-12-03 20:27 ` 2.6.24-rc3-mm2 Torsten Kaiser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=474EA914.1060502@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=balbir@in.ibm.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=nfs@lists.sourceforge.net \
--cc=samba-technical@lists.samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).