From: Sasha Levin <sashal@kernel.org>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: stable-commits@vger.kernel.org,
Jamal Hadi Salim <jhs@mojatatu.com>,
"David S. Miller" <davem@davemloft.net>,
stable@vger.kernel.org
Subject: Re: Patch "sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb" has been added to the 4.19-stable tree
Date: Mon, 5 Sep 2022 09:11:40 -0400 [thread overview]
Message-ID: <YxX1jNpOCRkYlD1J@sashalap> (raw)
In-Reply-To: <87sfl6yntg.fsf@toke.dk>
On Mon, Sep 05, 2022 at 03:04:43PM +0200, Toke Høiland-Jørgensen wrote:
>Sasha Levin <sashal@kernel.org> writes:
>
>> This is a note to let you know that I've just added the patch titled
>>
>> sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb
>>
>> to the 4.19-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:
>> sch_cake-return-__net_xmit_stolen-when-consuming-enq.patch
>> and it can be found in the queue-4.19 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.
>
>This patch was subsequently reverted; please drop it from all the stable
>trees. The patch to be backported instead is this one:
Yup, I took the revert too (makes tracking easier for us).
>9efd23297cca ("sch_sfb: Don't assume the skb is still around after enqueueing to child")
Looks like it's not in Linus's tree yet.
--
Thanks,
Sasha
next prev parent reply other threads:[~2022-09-05 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220905125828.1042711-1-sashal@kernel.org>
2022-09-05 13:04 ` Patch "sch_cake: Return __NET_XMIT_STOLEN when consuming enqueued skb" has been added to the 4.19-stable tree Toke Høiland-Jørgensen
2022-09-05 13:11 ` Sasha Levin [this message]
2022-09-05 13:56 ` Toke Høiland-Jørgensen
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=YxX1jNpOCRkYlD1J@sashalap \
--to=sashal@kernel.org \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=toke@toke.dk \
/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