From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, Christian Brauner <brauner@kernel.org>
Subject: Re: [RFC] possible way to deal with dup2() vs. allocated but still not opened descriptors
Date: Wed, 5 Jun 2024 03:39:27 +0100 [thread overview]
Message-ID: <20240605023927.GW1629371@ZenIV> (raw)
In-Reply-To: <20240605022855.GV1629371@ZenIV>
On Wed, Jun 05, 2024 at 03:28:55AM +0100, Al Viro wrote:
> Current solution is to have dup2() fail with -EBUSY. However,
> there's an approach that might avoid that wart. I'm not sure whether
> it's worth bothering with - it will have a cost, but then it might reduce
> the pingpong on current->files->file_lock.
Gah... Nevermind, that benefit is no longer there (and I really need
to get some sleep - only went "wait a sec, that lock hadn't been
taken in fd_install() since way back" after sending)
next prev parent reply other threads:[~2024-06-05 2:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 2:28 [RFC] possible way to deal with dup2() vs. allocated but still not opened descriptors Al Viro
2024-06-05 2:39 ` Al Viro [this message]
2024-06-05 14:23 ` Christian Brauner
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=20240605023927.GW1629371@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.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