linux-kernel - Re: [PATCH v16] sys_membarrier(): system-wide memory barrier (generic, x86)

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: <CAKgNAkh82_jTCELeAckhP=AVZGyxngSgo3g7SvLkD=aSdXSaxw@mail.gmail.com>
Date:	Thu, 23 Apr 2015 13:38:54 +0200
From:	"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
To:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc:	Davidlohr Bueso <dave@...olabs.net>,
	lkml <linux-kernel@...r.kernel.org>,
	Josh Triplett <josh@...htriplett.org>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Nicholas Miell <nmiell@...cast.net>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...hat.com>,
	Alan Cox <gnomes@...rguk.ukuu.org.uk>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	Stephen Hemminger <stephen@...workplumber.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	David Howells <dhowells@...hat.com>,
	Pranith Kumar <bobby.prani@...il.com>,
	"Carlos O'Donell" <carlos@...hat.com>
Subject: Re: [PATCH v16] sys_membarrier(): system-wide memory barrier
 (generic, x86)

Hi Mathieu,

On 22 April 2015 at 23:01, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com> wrote:
> ----- Original Message -----
>> On 22 April 2015 at 21:43, Mathieu Desnoyers
>> <mathieu.desnoyers@...icios.com> wrote:
>> > ----- Original Message -----
>> >> On Fri, 2015-04-17 at 11:06 -0400, Mathieu Desnoyers wrote:
>> >> > [ Not in this patch: tests (Pranith Kumar has a patch for this), man
>> >> > page.
>> >> > ]
>> >>
>> >> Actually, we had discussed that for new syscalls, the changelog _would_
>> >> be the manpage -- at least included in it.
>> >
>> > Do you want the formatted content, or just the text ? Putting
>> > manpage formatting in the changelog seems a bit odd.
>>
>>
>> Plain text works for me. Just divide it up into the usuual man-pages
>> sections (see man-pages(7), and I'll take care of the rest).
>
> OK. Should I do the writeup as a man(2) from the POV of a glibc
> user ? It's a bit different when we get to return values and
> error codes if we document kernel<->glibc or glibc<->user.

Ideally, from glibc POV, since that is the POV od user space consumers.

> Moreover, how can we get this into glibc ?

An eternal question...

https://lwn.net/Articles/534682/

I added Carlos, who can probably best summarize the current state of
things. I think there's a wiki discussion on this topic, but I could
not find a URL.

Cheers,

Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/