From: Jakub Kicinski <kuba@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, pabeni@redhat.com,
slipper.alive@gmail.com, stable-commits@vger.kernel.org
Subject: Re: Patch "net/ulp: prevent ULP without clone op from entering the LISTEN status" has been added to the 5.4-stable tree
Date: Thu, 12 Jan 2023 10:57:31 -0800 [thread overview]
Message-ID: <20230112105731.0da81d58@kernel.org> (raw)
In-Reply-To: <Y8AP6Lqo9sfX9Bb8@kroah.com>
On Thu, 12 Jan 2023 14:49:28 +0100 Greg KH wrote:
> On Thu, Jan 12, 2023 at 02:44:09PM +0100, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > net/ulp: prevent ULP without clone op from entering the LISTEN status
> >
> > to the 5.4-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> Oops, nope, this broke the build for 5.4 and older kernels, now
> dropping.
There's no clone op, right? If you're willing to futz with it I think
you just need to remove the "and the ops don't have ->clone" part of
the conditions. Any presence of ops on older kernels should make us
bail.
next prev parent reply other threads:[~2023-01-12 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16735310493146@kroah.com>
2023-01-12 13:49 ` Patch "net/ulp: prevent ULP without clone op from entering the LISTEN status" has been added to the 5.4-stable tree Greg KH
2023-01-12 18:57 ` Jakub Kicinski [this message]
2023-01-12 19:03 ` Greg KH
2023-01-13 11:41 ` Greg KH
2023-01-13 11:51 ` Paolo Abeni
2023-01-13 15:57 ` Greg KH
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=20230112105731.0da81d58@kernel.org \
--to=kuba@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=slipper.alive@gmail.com \
--cc=stable-commits@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