linux-kernel - Re: New syscalls (was: Re: linux-next: manual merge of the pidfd tree with the y2038 tree (now block and tip trees))

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK8P3a0iW-bhfiLY2po4cwaG0f-S+Xdoowrj0A6CwaY4VHgdWA@mail.gmail.com>
Date:   Tue, 12 Mar 2019 09:31:33 +0100
From:   Arnd Bergmann <arnd@...db.de>
To:     Christian Brauner <christian@...uner.io>
Cc:     Geert Uytterhoeven <geert@...ux-m68k.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Jens Axboe <axboe@...nel.dk>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux-Arch <linux-arch@...r.kernel.org>
Subject: Re: New syscalls (was: Re: linux-next: manual merge of the pidfd tree
 with the y2038 tree (now block and tip trees))

On Mon, Mar 11, 2019 at 10:43 PM Christian Brauner <christian@...uner.io> wrote:
> On Mon, Mar 11, 2019 at 10:38:07PM +0100, Arnd Bergmann wrote:
> > On Mon, Mar 11, 2019 at 9:36 AM Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> > >
> > > Shall each architcture maintainer take care of this hxxself, or will
> > > this be done in
> > > a coordinated way?
> >
> > I was planning to send a patch for all architectures this time
> > (after all three sets are merged, which is now), and ask future
>
> Just to clarify, are you referring to your sets? I think Linus hasn't
> gotten around to reviewing the PR for pidfd_send_signal() yet. :)

Ah, I thought he had already merged both, the confusion was on
my end.

      Arnd