[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190717024046.GI1506@brightrain.aerifal.cx>
Date: Tue, 16 Jul 2019 22:40:46 -0400
From: Rich Felker <dalias@...c.org>
To: Palmer Dabbelt <palmer@...ive.com>
Cc: viro@...iv.linux.org.uk, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-api@...r.kernel.org,
Arnd Bergmann <arnd@...db.de>, rth@...ddle.net,
ink@...assic.park.msu.ru, mattst88@...il.com,
linux@...linux.org.uk, catalin.marinas@....com, will@...nel.org,
tony.luck@...el.com, fenghua.yu@...el.com, geert@...ux-m68k.org,
monstr@...str.eu, ralf@...ux-mips.org, paul.burton@...s.com,
jhogan@...nel.org, James.Bottomley@...senPartnership.com,
deller@....de, benh@...nel.crashing.org, paulus@...ba.org,
mpe@...erman.id.au, heiko.carstens@...ibm.com, gor@...ux.ibm.com,
borntraeger@...ibm.com, ysato@...rs.sourceforge.jp,
davem@...emloft.net, luto@...nel.org, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, hpa@...or.com, x86@...nel.org,
peterz@...radead.org, acme@...nel.org,
alexander.shishkin@...ux.intel.com, jolsa@...hat.com,
namhyung@...nel.org, dhowells@...hat.com, firoz.khan@...aro.org,
stefan@...er.ch, schwidefsky@...ibm.com, axboe@...nel.dk,
christian@...uner.io, hare@...e.com, deepa.kernel@...il.com,
tycho@...ho.ws, kim.phillips@....com, linux-alpha@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-ia64@...r.kernel.org,
linux-m68k@...ts.linux-m68k.org, linux-mips@...r.kernel.org,
linux-parisc@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
linux-s390@...r.kernel.org, linux-sh@...r.kernel.org,
sparclinux@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: [PATCH v2 2/4] Add fchmodat4(), a new syscall
On Tue, Jul 16, 2019 at 06:27:17PM -0700, Palmer Dabbelt wrote:
> man 3p says that fchmodat() takes a flags argument, but the Linux
> syscall does not. There doesn't appear to be a good userspace
> workaround for this issue but the implementation in the kernel is pretty
> straight-forward. The specific use case where the missing flags came up
> was WRT a fuse filesystem implemenation, but the functionality is pretty
> generic so I'm assuming there would be other use cases.
Note that we do have a workaround in musl libc with O_PATH and
/proc/self/fd, but a syscall that allows a proper fix with the ugly
workaround only in the fallback path for old kernels will be much
appreciated!
What about also doing a new SYS_faccessat4 with working AT_EACCESS
flag? The workaround we have to do for it is far worse.
Rich
Powered by blists - more mailing lists