From: Maneesh Soni <maneesh@in.ibm.com>
To: Ethan Solomita <solo@google.com>
Cc: Dipankar Sarma <dipankar@in.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Greg KH <greg@kroah.com>, Martin Bligh <mbligh@google.com>,
Rohit Seth <rohitseth@google.com>,
viro@ftp.linux.org.uk, LKML <linux-kernel@vger.kernel.org>
Subject: Re: sysfs reclaim crash
Date: Wed, 28 Mar 2007 00:19:21 +0530 [thread overview]
Message-ID: <20070327184921.GA2057@in.ibm.com> (raw)
In-Reply-To: <46096202.6080205@google.com>
On Tue, Mar 27, 2007 at 11:27:14AM -0700, Ethan Solomita wrote:
> Hi Maneesh -- I will start testing with the patch you provided. If
> you come up with any further issues please let me know. Also, if you could
> suggest some additional BUG() lines that I could insert I would
> appreciate it. Since the bug is hard to reproduce, it may be easier to
> catch a race condition in the making via BUG() than an actual failure
> due to a race condition.
>
Hi Ethan,
Thanks for testing. The BUG_ON in sysfs_d_iput() is still there to catch
the first race we saw. And the second one should not occur as now we are not
using the s_dentry in sysfs_readdir().
Regards,
Maneesh
--
Maneesh Soni
Linux Technology Center,
IBM India Systems and Technology Lab,
Bangalore, India
next prev parent reply other threads:[~2007-03-27 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070319140238.cbf28b2b.akpm@linux-foundation.org>
[not found] ` <20070321134654.5wkqpfbpk0ggwks8@imap.linux.ibm.com>
[not found] ` <20070321182123.GA12602@in.ibm.com>
[not found] ` <20070323043047.GA5641@in.ibm.com>
[not found] ` <20070322210504.3b052139.akpm@linux-foundation.org>
[not found] ` <46042DDF.5060000@google.com>
2007-03-24 3:05 ` sysfs reclaim crash Maneesh Soni
2007-03-27 18:27 ` Ethan Solomita
2007-03-27 18:49 ` Maneesh Soni [this message]
2007-04-03 7:38 ` [PATCH] fix sysfs_readdir oops (was Re: sysfs reclaim crash) Maneesh Soni
2007-04-03 20:46 ` Ethan Solomita
2007-04-07 8:31 ` Tejun Heo
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=20070327184921.GA2057@in.ibm.com \
--to=maneesh@in.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dipankar@in.ibm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=rohitseth@google.com \
--cc=solo@google.com \
--cc=viro@ftp.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.