From: Tejun Heo <htejun@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, greg@kroah.com, cebbert@redhat.com,
sandeen@redhat.com, maneesh@in.ibm.com, cs@tequila.co.jp
Subject: Re: [PATCHSET 2.6.22-rc4] sysfs: fix race conditions
Date: Mon, 11 Jun 2007 15:15:39 +0900 [thread overview]
Message-ID: <466CE88B.2050803@gmail.com> (raw)
In-Reply-To: <20070610231203.730d0aba.akpm@linux-foundation.org>
Andrew Morton wrote:
>> This patchset contains three minimal backports of fixes in -mm. With
>> all patches in the patchset and sysfs-races.patch applied, kernel
>> survived ~20 hours of stress test without any problem.
>
> So these are being proposed for 2.6.22?
Yeap.
> I do wonder about Rafael's bug which he bisected down to
> gregkh-driver-sysfs-use-singly-linked-list-for-sysfs_dirent-tree.patch.
>
> If that won't be a problem in this patchset then I spose it's probably best
> to go ahead with a 2.6.22 merge, but it's more a Greg thing than a me
> thing.
I'm currently debugging that and it's irrelevant to these fixes. The
bug is introduced far after the fixes.
> I don't have a tree to merge these patches into, unless I drop all the
> patches which are in Greg's tree.
>
> Greg, can I leave it up to you to decide how we are to proceed here?
I can rebase all sysfs patches in -mm on top of linus#master + these
fixes if necessary.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-06-11 6:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 5:01 [PATCHSET 2.6.22-rc4] sysfs: fix race conditions Tejun Heo
2007-06-11 5:02 ` [PATCH 1/3] sysfs: store sysfs inode nrs in s_ino to avoid readdir oopses Tejun Heo
2007-06-11 5:03 ` [PATCH 2/3] sysfs: fix condition check in sysfs_drop_dentry() Tejun Heo
2007-06-11 5:04 ` [PATCH 3/3] sysfs: fix race condition around sd->s_dentry, take#2 Tejun Heo
2007-06-11 6:12 ` [PATCHSET 2.6.22-rc4] sysfs: fix race conditions Andrew Morton
2007-06-11 6:15 ` Tejun Heo [this message]
2007-06-12 0:54 ` Greg KH
2007-06-12 23:47 ` Greg KH
2007-06-13 4:50 ` Tejun Heo
2007-06-11 9:58 ` Eduard-Gabriel Munteanu
2007-06-11 10:02 ` Tejun Heo
2007-06-11 10:14 ` Eduard-Gabriel Munteanu
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=466CE88B.2050803@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cebbert@redhat.com \
--cc=cs@tequila.co.jp \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=sandeen@redhat.com \
/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).