From: Steve Dickson <SteveD@redhat.com>
To: Steven Timm <timm@fnal.gov>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS possible race condition, nfs_unlink vs. d_lookup
Date: Tue, 07 Mar 2006 07:36:16 -0500 [thread overview]
Message-ID: <440D7E40.9000401@RedHat.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0603030955060.11612@snowball.fnal.gov>
Sorry for the delayed response...
Steven Timm wrote:
> My question.. is the 2.4.21-37 kernel as distributed by Red Hat also
> vulnerable to this race condition?
Not that I'm aware of...
steved.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2006-03-07 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 15:57 NFS possible race condition, nfs_unlink vs. d_lookup Steven Timm
2006-03-03 20:47 ` Trond Myklebust
2006-03-03 21:15 ` Steven Timm
2006-03-03 21:22 ` Trond Myklebust
2006-03-07 12:36 ` Steve Dickson [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=440D7E40.9000401@RedHat.com \
--to=steved@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=timm@fnal.gov \
/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