From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Lutomirski Subject: Re: [PATCH v1 2/2] signal: add procfd_signal() syscall Date: Mon, 19 Nov 2018 16:34:00 -0800 Message-ID: References: <20181119103241.5229-1-christian@brauner.io> <20181119103241.5229-3-christian@brauner.io> <20181119223954.GA4992@cisco> <20181119230709.GB4992@cisco> <20181120003247.a776bej54baxqoxv@brauner.io> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <20181120003247.a776bej54baxqoxv@brauner.io> Sender: linux-kernel-owner@vger.kernel.org To: Christian Brauner Cc: Andrew Lutomirski , Tycho Andersen , Daniel Colascione , "Eric W. Biederman" , LKML , "Serge E. Hallyn" , Jann Horn , Andrew Morton , Oleg Nesterov , Aleksa Sarai , Al Viro , Linux FS Devel , Linux API , Tim Murray , linux-man , Kees Cook List-Id: linux-api@vger.kernel.org On Mon, Nov 19, 2018 at 4:33 PM Christian Brauner wrote: > > On Mon, Nov 19, 2018 at 04:27:49PM -0800, Andy Lutomirski wrote: > > On Mon, Nov 19, 2018 at 3:07 PM Tycho Andersen wrote: > > > > These tools also care about ioctls. Adding a system call is a pain, > > > > but the solution is to make adding system calls less of a pain, not to > > > > permanently make the Linux ABI worse. > > > > > > For user-defined values of "worse" :) > > > > > > > I tend to agree with Tycho here. But I'm wondering if it might be > > worth considering a better ioctl. > > > > /me dons flame-proof hat > > > > We could do: > > > > long better_ioctl(int fd, u32 nr, const void *inbuf, size_t inlen, > > const void *outbuf, size_t outlen); > > I'm the writer of this patch so take this with a grain of salt. > I think it is a bad idea to stop this patch and force us to introduce a > new type of ioctl(). I agree completely. > An ioctl() is also not easy to use for this task because we want to add > a siginfo_t argument which I actually think provides value and makes > this interface more useful. > You could always have a struct procfd_kill and pass a pointer to *that*. But sure, it's ugly.