All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: stfrench@microsoft.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ksmbd: the buffer of smb2 query dir response has at least 1" failed to apply to 5.15-stable tree
Date: Tue, 27 Aug 2024 08:57:48 +0200	[thread overview]
Message-ID: <2024082706-spray-simply-cd72@gregkh> (raw)
In-Reply-To: <CAKYAXd_7ipUOCPOOJTGCKWQOzcc34pX4dDHzG=d+O-4+o67kRA@mail.gmail.com>

On Tue, Aug 27, 2024 at 03:45:40PM +0900, Namjae Jeon wrote:
> On Tue, Aug 27, 2024 at 2:14 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Aug 27, 2024 at 11:54:56AM +0900, Namjae Jeon wrote:
> > > On Mon, Aug 26, 2024 at 8:38 PM <gregkh@linuxfoundation.org> wrote:
> > > >
> > > >
> > > > The patch below does not apply to the 5.15-stable tree.
> > > > If someone wants it applied there, or to any other stable or longterm
> > > > tree, then please email the backport, including the original git commit
> > > > id to <stable@vger.kernel.org>.
> > > As follows, I have marked stable tag(v6.1+) in patch to apply to 6.1
> > > kernel versions or later.
> > >
> > >  Cc: stable@vger.kernel.org # v6.1+
> >
> > Yes, but you also say:
> >
> >         Fixes: eb3e28c1e89b ("smb3: Replace smb2pdu 1-element arrays with flex-arrays")
> >
> > Which has been backported to the 5.10.y and 5.15.y kernel trees, so this
> > is why the FAILED email was triggered.
> >
> > > This patch does not need to be applied to 5.15 or 5.10.
> >
> > Are you sure?
> Yes, I have checked it.
> 5.10 : ksmbd is not here because it was merged into the 5.15 kernel.
> 5.15: smb client developer backported eb3e28c1e89b commit for only smb
> client's header.
> So it doesn't affect the ksmbd server.

Ok, thanks for looking into this.

> > If so, why is that the Fixes: tag?
> checkpatch.pl guide to add Fixes tag if there is a stable tag in the patch.
> 
> WARNING: The commit message has 'stable@', perhaps it also needs a 'Fixes:' tag?
> 
> In this case, I should not add fixes: tag...? I didn't know that.

No, it is correct to do so, smb is a bit odd in how things have been
backported recently to different kernel trees, so all is good.

Thanks!

greg k-h

      reply	other threads:[~2024-08-27  6:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26 11:38 FAILED: patch "[PATCH] ksmbd: the buffer of smb2 query dir response has at least 1" failed to apply to 5.15-stable tree gregkh
2024-08-27  2:54 ` Namjae Jeon
2024-08-27  5:14   ` Greg KH
2024-08-27  6:45     ` Namjae Jeon
2024-08-27  6:57       ` 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=2024082706-spray-simply-cd72@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linkinjeon@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=stfrench@microsoft.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.