From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] LSM file locking patch is bogus
Date: 8 Aug 2002 20:59:59 -0700 [thread overview]
Message-ID: <aivenv$r6t$1@cesium.transmeta.com> (raw)
In-Reply-To: Pine.LNX.4.44.0207272011001.3897-100000@home.transmeta.com
Followup to: <Pine.LNX.4.44.0207272011001.3897-100000@home.transmeta.com>
By author: Linus Torvalds <torvalds@transmeta.com>
In newsgroup: linux.dev.fs.devel
>
> This should be a non-issue, since current 2.5.x passes the "struct file"
> pointer around, not the file descriptor. So there should be no race,
> because everybody uses the same "struct file *" everywhere, and nobody
> re-gets the file pointer twice any more.
>
> (Yeah, I'm too lazy to double-check that this is 100% true, but it
> _should_ all have been fixed a few weeks ago).
>
Does that mean that opening /proc/*/fd/* actually dup()s the file
descriptor as one should expect?
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-08-09 4:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 22:31 [PATCH] LSM file locking patch is bogus Matthew Wilcox
2002-07-28 3:02 ` Seth Arnold
2002-07-28 3:13 ` Linus Torvalds
2002-08-09 3:59 ` H. Peter Anvin [this message]
2002-07-28 18:47 ` Greg KH
2002-07-29 23:58 ` Chris Wright
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='aivenv$r6t$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--cc=linux-fsdevel@vger.kernel.org \
/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