public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dan Aloni <dan@kernelim.com>
Cc: linux-kernel@vger.kernel.org, Steve French <sfrench@samba.org>,
	stable@vger.kernel.org, linux-cifs@vger.kernel.org
Subject: Re: [PATCH stable] cifs: empty TargetInfo leads to crash on recovery
Date: Tue, 13 Feb 2018 16:38:13 +0100	[thread overview]
Message-ID: <20180213153813.GA5919@kroah.com> (raw)
In-Reply-To: <20180128145220.GA47771@gmail.com>

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

      reply	other threads:[~2018-02-13 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-27 20:07 [PATCH stable] cifs: empty TargetInfo leads to crash on recovery Dan Aloni
2018-01-28 14:43 ` Greg KH
2018-01-28 14:52   ` Dan Aloni
2018-02-13 15:38     ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180213153813.GA5919@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dan@kernelim.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfrench@samba.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox