From: Phil Dier <phil@icglink.com>
To: linux-kernel@vger.kernel.org
Cc: ziggy@icglink.com, scott@icglink.com, jack@icglink.com
Subject: Re: 2.6.13-rc6 Oops with Software RAID, LVM, JFS, NFS
Date: Mon, 15 Aug 2005 12:44:04 -0500 [thread overview]
Message-ID: <20050815124404.089ffe64.phil@icglink.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0508142119460.6740@montezuma.fsmlabs.com>
On Sun, 14 Aug 2005 21:20:35 -0600 (MDT)
Zwane Mwaikambo <zwane@arm.linux.org.uk> wrote:
> On Sun, 14 Aug 2005, Robert Love wrote:
>
> > On Sun, 2005-08-14 at 20:40 -0600, Zwane Mwaikambo wrote:
> >
> > > I'm new here, if the inode isn't being watched, what's to stop d_delete
> > > from removing the inode before fsnotify_unlink proceeds to use it?
> >
> > Nothing. But check out
> >
> > http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7a91bf7f5c22c8407a9991cbd9ce5bb87caa6b4a
>
> That git web interface looks rather spiffy.
>
> > Should solve this problem?
>
> Seems to fit the bill perfectly.
>
> Thanks,
> Zwane
>
So, for the record, I patched my 2.6.13-rc6 kernel with the patch at this location:
http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=7a91bf7f5c22c8407a9991cbd9ce5bb87caa6b4a;hp=1963c907b21e140082d081b1c8f8c2154593c7d7
and I will be testing it today.
Thanks to all of you guys.
--
Phil Dier (ICGLink.com -- 615 370-1530 x733)
/* vim:set noai nocindent ts=8 sw=8: */
prev parent reply other threads:[~2005-08-15 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 15:59 2.6.13-rc6 Oops with Software RAID, LVM, JFS, NFS Phil Dier
2005-08-12 2:07 ` Neil Brown
2005-08-12 4:17 ` Phil Dier
2005-08-12 17:35 ` Phil Dier
2005-08-12 18:35 ` Sonny Rao
2005-08-15 2:03 ` Phil Dier
2005-08-15 2:40 ` Zwane Mwaikambo
2005-08-15 3:08 ` Robert Love
2005-08-15 3:20 ` Zwane Mwaikambo
2005-08-15 17:44 ` Phil Dier [this message]
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=20050815124404.089ffe64.phil@icglink.com \
--to=phil@icglink.com \
--cc=jack@icglink.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@icglink.com \
--cc=ziggy@icglink.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 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.