From: Seebs <seebs@seebs.net>
To: Ross Burton <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH][RFC] pseudo: intercept syscall() and return ENOTSUP for renameat2
Date: Tue, 27 Mar 2018 10:53:31 -0500 [thread overview]
Message-ID: <20180327105331.17fc7d86@seebsdell> (raw)
In-Reply-To: <20180327154802.14611-1-ross.burton@intel.com>
On Tue, 27 Mar 2018 16:48:02 +0100
Ross Burton <ross.burton@intel.com> wrote:
> This patch intercepts syscall() and returns ENOTSUP if renameat2() is
> being called.
I am inclined to NAK this until we have a clearer understanding of the
mechanics observed in glibc's syscall implementation; it's doing magic
that this will not do, and will in fact undo, and we don't know *why*
it does that magic. It seems dangerous to break a thing without first
knowing why it was there in the first place.
If we want to wrap this, at a bare minimum, we should be using a
custom wrapper which doesn't use any of the standard wrapper magic. At
that point, we can *probably* pass args along and just return
immediately after the real_syscall call and get usable results? (And
bail prematurely if it's a call we need to prevent.)
-s
next prev parent reply other threads:[~2018-03-27 15:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 15:48 [PATCH][RFC] pseudo: intercept syscall() and return ENOTSUP for renameat2 Ross Burton
2018-03-27 15:53 ` Seebs [this message]
2018-03-27 16:02 ` ✗ patchtest: failure for " Patchwork
2018-03-27 22:43 ` [PATCH][RFC] " Andre McCurdy
2018-03-28 9:15 ` Burton, Ross
2018-03-31 4:15 ` Andre McCurdy
2018-03-31 5:06 ` Seebs
2018-03-31 6:02 ` Andre McCurdy
2018-03-31 15:35 ` Seebs
2018-03-31 15:58 ` Bruce Ashfield
2018-03-31 13:12 ` Richard Purdie
2018-03-31 15:39 ` Seebs
2018-03-31 21:03 ` Joshua Watt
2018-03-31 21:16 ` Seebs
2018-04-02 22:20 ` Richard Purdie
2018-04-04 21:28 ` Khem Raj
2018-04-04 21:45 ` Seebs
2018-04-05 0:29 ` Khem Raj
2018-04-04 21:51 ` Andre McCurdy
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=20180327105331.17fc7d86@seebsdell \
--to=seebs@seebs.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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