From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <stephen@networkplumber.org>
Cc: <netdev@vger.kernel.org>
Subject: Fw: [Bug 216694] New: [Syzkaller & bisect] There is inet_csk_get_port WARNING in v6.1-rc4 kernel
Date: Wed, 16 Nov 2022 09:12:53 -0800 [thread overview]
Message-ID: <20221116171253.47853-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20221116085854.0dcfa44d@hermes.local>
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Wed, 16 Nov 2022 08:58:54 -0800
> Begin forwarded message:
>
> Date: Wed, 16 Nov 2022 08:44:26 +0000
> From: bugzilla-daemon@kernel.org
> To: stephen@networkplumber.org
> Subject: [Bug 216694] New: [Syzkaller & bisect] There is inet_csk_get_port WARNING in v6.1-rc4 kernel
>
>
> https://bugzilla.kernel.org/show_bug.cgi?id=216694
>
> Bug ID: 216694
> Summary: [Syzkaller & bisect] There is inet_csk_get_port
> WARNING in v6.1-rc4 kernel
> Product: Networking
> Version: 2.5
> Kernel Version: v6.1-rc4
> Hardware: All
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> Assignee: stephen@networkplumber.org
> Reporter: pengfei.xu@intel.com
> Regression: No
>
> "WARNING inet_csk_get_port" is found in v6.1-rc4 kernel.
>
> And first bad commit is: 28044fc1d4953b07acec0da4d2fc4784c57ea6fb
> "net: Add a bhash2 table hashed by port and address"
>
> Reproduced code from syzkaller, kconfig and full information is in the link:
> https://github.com/xupengfe/syzkaller_logs/tree/main/221108_215733_inet_csk_get_port
>
>
> Related discusstion link in LKML community:
> https://lore.kernel.org/lkml/Y2xyHM1fcCkh9AKU@xpf.sh.intel.com/
I'm working on the issue and will post a fix.
https://lore.kernel.org/netdev/20221110201925.96741-1-kuniyu@amazon.com/
https://lore.kernel.org/netdev/20221110203432.97668-1-kuniyu@amazon.com/
Thank you!
prev parent reply other threads:[~2022-11-16 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 16:58 Fw: [Bug 216694] New: [Syzkaller & bisect] There is inet_csk_get_port WARNING in v6.1-rc4 kernel Stephen Hemminger
2022-11-16 17:12 ` Kuniyuki Iwashima [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=20221116171253.47853-1-kuniyu@amazon.com \
--to=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.