public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pengfei Xu <pengfei.xu@intel.com>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <heng.su@intel.com>
Subject: Re: [Syzkaller] There is inet_csk_get_port WARNING in v6.1-rc4 kernel
Date: Fri, 11 Nov 2022 13:49:13 +0800	[thread overview]
Message-ID: <Y23iWU/hpUGpdqVf@xpf.sh.intel.com> (raw)
In-Reply-To: <CAJnrk1ZvWfSAsYx-cErCqjQbciKCiAKss6Kvcm_4vXP5bzFh2g@mail.gmail.com>

Hi Joanne Koong,

On 2022-11-10 at 10:37:36 -0800, Joanne Koong wrote:
> On Wed, Nov 9, 2022 at 7:38 PM Pengfei Xu <pengfei.xu@intel.com> wrote:
> >
> > Hi Joanne Koong and net developer,
> >
> > Greeting!
> >
> > Soft remind: "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"
> >
> > Reproduce code from syzkaller, kconfig and bisect info are in attached.
> > Full information is in the link:
> > https://github.com/xupengfe/syzkaller_logs/tree/main/221108_215733_inet_csk_get_port
> >
> > Thanks!
> > BR.
> 
> Thanks for your email. This has the same root cause (handling the
> error case when connect() fails) as the issue discussed in this thread
> https://lore.kernel.org/netdev/20221029001249.86337-1-kuniyu@amazon.com/.
> After consensus is reached in this thread, I'll submit a follow-up
> fix; I'm hoping to submit it by the end of next week at the latest.

Great! Thanks for your link!
And hope the repro.c and above info is helpful.

Thanks!
BR.

      reply	other threads:[~2022-11-11  5:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  3:38 [Syzkaller] There is inet_csk_get_port WARNING in v6.1-rc4 kernel Pengfei Xu
2022-11-10 18:37 ` Joanne Koong
2022-11-11  5:49   ` Pengfei Xu [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=Y23iWU/hpUGpdqVf@xpf.sh.intel.com \
    --to=pengfei.xu@intel.com \
    --cc=heng.su@intel.com \
    --cc=joannelkoong@gmail.com \
    --cc=linux-kernel@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