linux-kernel - Re: [PATCH stable] cifs: empty TargetInfo leads to crash on recovery

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:   Tue, 13 Feb 2018 16:38:13 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Dan Aloni <dan@...nelim.com>
Cc:     linux-kernel@...r.kernel.org, Steve French <sfrench@...ba.org>,
        stable@...r.kernel.org, linux-cifs@...r.kernel.org
Subject: Re: [PATCH stable] cifs: empty TargetInfo leads to crash on recovery

On Sun, Jan 28, 2018 at 04:52:20PM +0200, Dan Aloni wrote:
> On Sun, Jan 28, 2018 at 03:43:48PM +0100, Greg KH wrote:
> > On Sat, Jan 27, 2018 at 10:07:41PM +0200, Dan Aloni wrote:
> > > commit cabfb3680f78 upstream.
> > 
> > Are you sure?
> > $ gsr cabfb3680f78
> > cabfb3680f78 ("CIFS: Enable encryption during session setup phase")
> > 
> > Doesn't seem to match up at all here :(
> 
> That's only because it fixed the issue unknownly, accordingly to
> git-bisectings I've done. Should I have not added 'commit <githash>
> upstream.' in that case? stable_kernel_rules.txt is not so clear
> about it.

I need the git commit id of the patch that is in Linus's tree in order
to apply it to the stable tress.  And the text and comments and change
needs to match.  To have a different subject would be really confusing.

You can put a note in the changelog body that says

[note this fixes issue x and y - myname]

which is what some people do.

Care to fix this up and resend?

thanks,

greg k-h