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  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:	Thu, 24 Jul 2014 14:47:47 -0700
From:	Andrew Morton <>
To:	David Herrmann <>
	Michael Kerrisk <>,
	Ryan Lortie <>,
	Linus Torvalds <>,,,, Greg Kroah-Hartman <>,,
	Lennart Poettering <>,
	Daniel Mack <>, Kay Sievers <>,
	Hugh Dickins <>,
	Andy Lutomirski <>,
	Alexander Viro <>
Subject: Re: [PATCH v4 0/6] File Sealing & memfd_create()

On Sun, 20 Jul 2014 19:34:34 +0200 David Herrmann <> wrote:

> This is v4 of the File-Sealing and memfd_create() patches. You can find v1 with
> a longer introduction at gmane [1], there's also v2 [2] and v3 [3] available.
> See also the article about sealing on LWN [4], and a high-level introduction on
> the new API in my blog [5]. Last but not least, man-page proposals are
> available in my private repository [6].
> ...
> [1]    memfd v1:
> [2]    memfd v2:
> [3]    memfd v3:
> [4] LWN article:
> [5]   API Intro:
> [6]   Man-pages:
> [7]    Dev-repo:

This is unconventional and a little irritating.  I'm OK with running
around chasing down web pages but we generally don't do that in
changelogs.  I'm not sure why really, maybe partly because things
bitrot, partly because that's where people expect to find things,
partly because people like work down caves and on airplanes ;)

Another downside is that if a reviewer wants to comment on some piece
of text, it isn't available for the usual reply-to-all quoting.

So...  Could you please put together a plain old text/plain changelog
which actually describes this patchset and send it along?  Everything
which people need/want to know, all in one place?  That text should be
maintained alongside the patches themselves, should there be future

Now excuse me, I have a bunch of web pages to go and read ;)

<reads "[1]    memfd v1">

OK, I immediately have questions and I see significant review feedback,
so either that document is out of date or that review feedback was

Help.  Where do I (and all future readers of these patches) go to get
an up to date and complete description of this patchset??
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists