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] [day] [month] [year] [list]
Date:	Sun, 06 Mar 2016 21:03:55 +0100
From:	Nicolai Stange <nicstange@...il.com>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	Nicolai Stange <nicstange@...il.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Alexander Viro <viro@...iv.linux.org.uk>,
	Jonathan Corbet <corbet@....net>, Jan Kara <jack@...e.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Julia Lawall <Julia.Lawall@...6.fr>,
	Gilles Muller <Gilles.Muller@...6.fr>,
	Nicolas Palix <nicolas.palix@...g.fr>,
	Michal Marek <mmarek@...e.com>, linux-kernel@...r.kernel.org,
	cocci@...teme.lip6.fr
Subject: Re: [PATCH v4 0/8] fix debugfs file removal races

Greg Kroah-Hartman <gregkh@...uxfoundation.org> writes:

> On Sun, Mar 06, 2016 at 01:54:40PM +0100, Nicolai Stange wrote:
>> Greg Kroah-Hartman <gregkh@...uxfoundation.org> writes:
>> 
>> > On Tue, Feb 23, 2016 at 02:51:25PM +0100, Nicolai Stange wrote:
>> >> The changes from v3 to v4 are style changes regarding the Coccinelle
>> >> part only -- it has been split off from former [3/7] into its own
>> >> patch [4/8].
>> >> 
>> >> The big step has been from v2 to v3 and these changes haven't got any
>> >> review yet.
>> >
>> > Well, given that they look sane to me, I've applied them to my tree,
>> > let's see what breaks in linux-next now :)
>> 
>> Great, thank you!
>> 
>> Unfortunately, the kbuild test robot detected two minor issues and I've
>> sent v5 in order to correct this.
>> 
>> In case that it isn't possible to simply replace v4 by v5, please let me
>> know and I'll send two fixup patches instead.
>
> What do the fixup patches look like?  That might be easier to take if
> they aren't really major issues (one was a documentation issue, which
> isn't a big deal...)

I sent the two fixup patches as a proposal in a series of their own:
http://lkml.kernel.org/g/1457294345-4588-1-git-send-email-nicstange@gmail.com

Thank you!

Nicolai

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ