From: Florian Westphal <fw@strlen.de>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: edumazet@google.com, davem@davemloft.net, dsahern@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com, threeearcat@gmail.com
Subject: Re: general protection fault in raw_seq_start
Date: Fri, 31 Mar 2023 12:36:30 +0200 [thread overview]
Message-ID: <20230331103630.GE22079@breakpoint.cc> (raw)
In-Reply-To: <20230331071725.66950-1-kuniyu@amazon.com>
Kuniyuki Iwashima <kuniyu@amazon.com> wrote:
> And I found this seems wrong.
>
> c25b7a7a565e ("inet: ping: use hlist_nulls rcu iterator during lookup")
How so?
next prev parent reply other threads:[~2023-03-31 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 12:12 general protection fault in raw_seq_start Dae R. Jeong
2023-03-30 21:55 ` Kuniyuki Iwashima
2023-03-31 5:31 ` Jason Xing
2023-03-31 7:04 ` Eric Dumazet
2023-03-31 7:17 ` Kuniyuki Iwashima
2023-03-31 10:36 ` Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-31 5:40 Iwashima, Kuniyuki
2023-03-31 6:14 ` Jason Xing
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=20230331103630.GE22079@breakpoint.cc \
--to=fw@strlen.de \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=threeearcat@gmail.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).