From: Eric Dumazet <eric.dumazet@gmail.com>
To: Vasily Averin <vvs@virtuozzo.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
Hao Sun <sunhao.th@gmail.com>,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: WARNING in sk_stream_kill_queues
Date: Sat, 4 Sep 2021 10:14:39 -0700 [thread overview]
Message-ID: <606daddf-6ca5-6789-b571-6178100432be@gmail.com> (raw)
In-Reply-To: <71e8b315-3f3a-85ae-fede-914269a15272@virtuozzo.com>
On 9/4/21 7:48 AM, Vasily Averin wrote:
> Eric,
> this problem is not related to my patches.
> I've reproduced the problem locally on orignal kernel with original config,
> then I've applied last version of my patch -- but it did not help, issue was reproduced again,
> then I've reverted all my patches, see lest below -- and reproduced the problem once again
>
> Thank you,
> Vasily Averin
>
> b8a0bb68ac30 (HEAD -> net-next-5.15) Revert "ipv6: allocate enough headroom in ip6_finish_output2()"
> 1bc2de674a1b Revert "ipv6: ip6_finish_output2: set sk into newly allocated nskb"
> 780e2f7d9b93 Revert "skbuff: introduce skb_expand_head()"
> 782eaeed9de7 Revert "ipv6: use skb_expand_head in ip6_finish_output2"
> 639e9842fc1f Revert "ipv6: use skb_expand_head in ip6_xmit"
> 3b16ee164bcd Revert "ipv4: use skb_expand_head in ip_finish_output2"
> ab48caf0e632 Revert "vrf: use skb_expand_head in vrf_finish_output"
> 4da67a72ceef Revert "ax25: use skb_expand_head"
> 9b113a8a62f0 Revert "bpf: use skb_expand_head in bpf_out_neigh_v4/6"
> fc4ab503ce8f Revert "vrf: fix NULL dereference in vrf_finish_output()"
>
OK, thanks for checking.
The repro on my host does not trigger the issue, I can not really investigate/bisect.
next prev parent reply other threads:[~2021-09-04 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 7:54 WARNING in sk_stream_kill_queues Hao Sun
2021-09-03 16:56 ` Eric Dumazet
2021-09-03 18:10 ` Vasily Averin
2021-09-04 14:48 ` Vasily Averin
2021-09-04 17:14 ` Eric Dumazet [this message]
2021-09-04 17:23 ` Vasily Averin
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=606daddf-6ca5-6789-b571-6178100432be@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sunhao.th@gmail.com \
--cc=vvs@virtuozzo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).