linux-kernel - Re: [stable] Failing to send a CLOSE if file is opened WRONLY and server reboots on a 4.x mount

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]

Message-ID: <20151118232029.GA10848@charon>
Date:	Wed, 18 Nov 2015 23:20:29 +0000
From:	Luis Henriques <luis.henriques@...onical.com>
To:	Ben Hutchings <ben@...adent.org.uk>
Cc:	Willy Tarreau <w@....eu>,
	"stable@...r.kernel.org" <stable@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Trond Myklebust <trond.myklebust@...marydata.com>,
	"Kornievskaia, Olga" <Olga.Kornievskaia@...app.com>
Subject: Re: [stable] Failing to send a CLOSE if file is opened WRONLY and
 server reboots on a 4.x mount

On Sun, Nov 15, 2015 at 12:53:21AM +0000, Ben Hutchings wrote:
> On Wed, 2015-09-16 at 07:33 +0200, Willy Tarreau wrote:
> > Hi Olga,
> > 
> > On Tue, Sep 15, 2015 at 02:36:06PM +0000, Kornievskaia, Olga wrote:
> > > 
> > > Hi Willy,
> > > 
> > > After checking with the list, I believe the course of action will be to
> > > correct the patch with the patch below instead of reverting it.
> > 
> > OK but as far as I can tell, mainline is still not fixed regarding this
> > issue. I can't introduce in a stable branch a fix which is not yet in
> > mainline. Thus I'll simply remove the patch from this series and will
> > merge both patches in a future series once your fix reaches mainline.
> > 
> > Note that I picked this fix from 3.2 (commit ef8500b18fc4bb) so my
> > understanding is that this patch needs to be reverted from 3.2 as well
> > for the time being ?
> > 
> > Thanks very much for the detailed investigations!
> 
> The second patch is now in mainline as commit
> a41cbe86df3afbc82311a1640e20858c0cd7e065, and appears to be needed on
> all stable branches since they all got the previous incorrect patch.
> 

Thanks, queuing it for the 3.16 kernel.

Cheers,
--
Luís
--
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/