From: Dipankar Sarma <dipankar@in.ibm.com>
To: Anton Blanchard <anton@samba.org>
Cc: "Peter J. Braam" <braam@clusterfs.com>,
linux-kernel@vger.kernel.org, hch@infradead.org, axboe@suse.de,
lmb@suse.de, kevcorry@us.ibm.com, arjanv@redhat.com,
iro@parcelfarce.linux.theplanet.co.uk,
trond.myklebust@fys.uio.no, lustre-devel@clusterfs.com
Subject: Re: [PATCH/RFC] Lustre VFS patch, version 2
Date: Mon, 7 Jun 2004 23:32:51 +0530 [thread overview]
Message-ID: <20040607180251.GA6416@in.ibm.com> (raw)
In-Reply-To: <20040604165548.GC20820@krispykreme>
On Sat, Jun 05, 2004 at 02:55:48AM +1000, Anton Blanchard wrote:
>
> > 10. "Have these patches undergone any siginifant test?" by Anton Blanchard:
> >
> > There are two important questions I think:
> > - Do the patches cause damage?
> > Probably not anymore. SUSE has done testing and it appears the
> > original patch I attached didn't break things (after one fix was
> > made).
>
> IBM did a lot of the work on that issue and it took the better part of a
> week to find, fix and verify.
AFAIK, Maneesh asked about revalidate_special() returning negative dentries
and no checking of it in path lookup(), but got no reply from Lustre
folks. It is clearly broken. Maneesh has more breakage from Lustre
VFS patches now. It would be helpful if they atleast comment on
fixes for those.
Thanks
Dipankar
next prev parent reply other threads:[~2004-06-07 18:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 23:15 [PATCH/RFC] Lustre VFS patch, version 2 Peter J. Braam
2004-06-03 13:59 ` Christoph Hellwig
2004-06-03 14:19 ` Lars Marowsky-Bree
2004-06-03 14:26 ` Christoph Hellwig
2004-06-03 14:33 ` Christoph Hellwig
2004-06-03 14:49 ` Trond Myklebust
2004-06-03 18:10 ` Jan Harkes
2004-06-04 5:03 ` Daniel Phillips
2004-06-03 14:27 ` Christoph Hellwig
2004-06-04 16:55 ` Anton Blanchard
2004-06-07 18:02 ` Dipankar Sarma [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-03 15:53 Peter J. Braam
2004-06-06 17:00 ` Christoph Hellwig
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=20040607180251.GA6416@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=anton@samba.org \
--cc=arjanv@redhat.com \
--cc=axboe@suse.de \
--cc=braam@clusterfs.com \
--cc=hch@infradead.org \
--cc=iro@parcelfarce.linux.theplanet.co.uk \
--cc=kevcorry@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
--cc=lustre-devel@clusterfs.com \
--cc=trond.myklebust@fys.uio.no \
/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