public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Ilya Maximets <i.maximets@ovn.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
	echaudro@redhat.com, Aaron Conole <aconole@redhat.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: Patch "openvswitch: Stricter validation for the userspace action" has been added to the 6.15-stable tree
Date: Sat, 21 Jun 2025 04:10:47 -0400	[thread overview]
Message-ID: <aFZpB3maNj3z2t18@lappy> (raw)
In-Reply-To: <6d21ab64-88f9-4380-9e28-63700bddbe30@ovn.org>

On Fri, Jun 20, 2025 at 10:04:44AM +0200, Ilya Maximets wrote:
>On 6/20/25 4:32 AM, Sasha Levin wrote:
>> This is a note to let you know that I've just added the patch titled
>>
>>     openvswitch: Stricter validation for the userspace action
>>
>> to the 6.15-stable tree which can be found at:
>>     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>>
>> The filename of the patch is:
>>      openvswitch-stricter-validation-for-the-userspace-ac.patch
>> and it can be found in the queue-6.15 subdirectory.
>>
>> If you, or anyone else, feels it should not be added to the stable tree,
>> please let <stable@vger.kernel.org> know about it.
>
>FWIW, backporting of this change was previously discussed here:
>  https://lore.kernel.org/netdev/2025060520-slacking-swimmer-1b31@gregkh/
>
>With the conclusion to drop it as it's not a bug fix and hence there is
>no reason to backport it.

Dropped, thanks!

-- 
Thanks,
Sasha

      reply	other threads:[~2025-06-21  8:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250620023232.2605858-1-sashal@kernel.org>
2025-06-20  8:04 ` Patch "openvswitch: Stricter validation for the userspace action" has been added to the 6.15-stable tree Ilya Maximets
2025-06-21  8:10   ` Sasha Levin [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=aFZpB3maNj3z2t18@lappy \
    --to=sashal@kernel.org \
    --cc=aconole@redhat.com \
    --cc=davem@davemloft.net \
    --cc=echaudro@redhat.com \
    --cc=edumazet@google.com \
    --cc=greg@kroah.com \
    --cc=horms@kernel.org \
    --cc=i.maximets@ovn.org \
    --cc=kuba@kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable-commits@vger.kernel.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