From: Al Viro <viro@zeniv.linux.org.uk>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Nir Lichtman <nir@lichtman.org>,
Tycho Andersen <tandersen@netflix.com>,
Vegard Nossum <vegard.nossum@oracle.com>,
linux-security-module@vger.kernel.org
Subject: Re: [GIT PULL] execve updates for v6.13-rc1 (take 2)
Date: Fri, 29 Nov 2024 04:48:45 +0000 [thread overview]
Message-ID: <20241129044845.GJ3387508@ZenIV> (raw)
In-Reply-To: <87h67qoeh5.fsf@email.froward.int.ebiederm.org>
On Thu, Nov 28, 2024 at 10:23:18PM -0600, Eric W. Biederman wrote:
> > I agree that for fexecve() the only sane approach is to go by whatever
> > that opened file refers to; I'm not sold on the _usefulness_ of
> > fexecve() to start with, but if we want that thing, that's the way
> > to go.
>
> The craziness is that apparently systemd wants to implement execve in
> terms of fexecve, not execveat.
... presumably because the pathname might have changed its meaning
just as we called execve(). Which is why we want it to show up in
comm, got it.
</sarcasm>
next prev parent reply other threads:[~2024-11-29 4:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202411210651.CD8B5A3B98@keescook>
[not found] ` <CAHk-=wjMagH_5-_8KhAOJ+YSjXUR5FELYxFgqtWBHOhKyUzGxA@mail.gmail.com>
[not found] ` <05F133C4-DB2D-4186-9243-E9E18FCBF745@kernel.org>
[not found] ` <CAHk-=wgEjs8bwSMSpoyFRiUT=_NEFzF8BXFEvYzVQCu8RD=WmA@mail.gmail.com>
[not found] ` <202411271645.04C3508@keescook>
[not found] ` <CAHk-=wi+_a9Y8DtEp2P9RnDCjn=gd4ym_5ddSTEAadAyzy1rkw@mail.gmail.com>
[not found] ` <20241128020558.GF3387508@ZenIV>
[not found] ` <CAHk-=whb+V5UC0kuJkBByeEkeRGyLhTupBvpF-z57Hvmn7kszA@mail.gmail.com>
[not found] ` <13223528-74FF-4B68-B0CF-25DCC995D0A0@kernel.org>
[not found] ` <CAHk-=wgKgi5eqo6oW0bBS2-Cr+d4jraoKfVq6wbmdiWWsZbMLw@mail.gmail.com>
[not found] ` <20241129033419.GI3387508@ZenIV>
2024-11-29 4:23 ` [GIT PULL] execve updates for v6.13-rc1 (take 2) Eric W. Biederman
2024-11-29 4:48 ` Al Viro [this message]
2024-11-29 17:00 ` Casey Schaufler
2024-11-29 19:33 ` Eric W. Biederman
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=20241129044845.GJ3387508@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=casey@schaufler-ca.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=ebiederm@xmission.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=nir@lichtman.org \
--cc=tandersen@netflix.com \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).