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]
Date:   Wed, 15 Nov 2017 17:30:20 +0100 (CET)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Ingo Molnar <mingo@...nel.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Andy Lutomirski <luto@...nel.org>,
        Borislav Petkov <bp@...e.de>,
        Andrew Morton <akpm@...ux-foundation.org>,
        "H. Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <a.p.zijlstra@...llo.nl>,
        Andy Lutomirski <luto@...nel.org>
Subject: Re: linux-next: manual merge of the rseq tree with Linus' tree

On Wed, 15 Nov 2017, Mathieu Desnoyers wrote:

> ----- On Nov 15, 2017, at 11:04 AM, Thomas Gleixner tglx@...utronix.de wrote:
> 
> > On Wed, 15 Nov 2017, Mathieu Desnoyers wrote:
> >> ----- On Nov 15, 2017, at 10:22 AM, Thomas Gleixner tglx@...utronix.de wrote:
> >> > Can we please handle this as any other feature which is not ready before
> >> > the merge window and postpone the rseq stuff for 4.16?
> >> 
> >> Linus showed interest in merging the rseq tree when we discussed at the
> >> Kernel Summit. The tree has not changed much since then. I only integrated
> >> membarrier patches that were implemented around the time of the 4.14 merge
> >> window, which I queued for the 4.15 (current) window.
> > 
> > Linus showed interest for a lot of things in the past. That does not mean
> > it makes things magically complete and ready.
> > 
> > As Michael pointed out there is no man page, not even a draft for it
> > available. See: Documentation/process/adding-syscalls.rst
> 
> The rseq commit has a manpage associated for seq. The cpu_opv does not have it
> yet, nor the new membarrier commands. I plan to write those quickly after the
> tree reaches master.

And that's a special rule for you, right?

Documentation/process/adding-syscalls.rst is for everybody else who
implements a new syscall.

Thanks,

	tglx

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ