mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pengfei Xu <pengfei.xu@intel.com>
To: Eyal Birger <eyal.birger@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <heng.su@intel.com>
Subject: Re: [syzkaller] There is "lwtunnel_valid_encap_type" WARNING in 6.1-rc3 mainline kernel
Date: Mon, 7 Nov 2022 16:16:16 +0800	[thread overview]
Message-ID: <Y2i+0N5zkwxmuyNO@xpf.sh.intel.com> (raw)
In-Reply-To: <CAHsH6Gt92EH7eC5MyL23G7ySYk4OyNoC9U=0Y7vXbbqVyyZ7SQ@mail.gmail.com>

Hi Eyal,

On 2022-11-07 at 08:09:39 +0200, Eyal Birger wrote:
> Hi,
> 
> On Mon, Nov 7, 2022 at 5:27 AM Pengfei Xu <pengfei.xu@intel.com> wrote:
> >
> > Hi Birger and net expert,
> >
> > Greeting!
> >
> > There is "lwtunnel_valid_encap_type" WARNING in 6.1-rc3 mainline kernel in syzkaller test in guest:
> 
> <snip>
> 
> >
> > Bisect and found the first bad commit is 2c2493b9da9166478fe072e3054f8a5741dadb02.
> > "xfrm: lwtunnel: add lwtunnel support for xfrm interfaces in collect_md mode"
> > And revert this commit, this issue could not be reproduced.
> >
> > All bisect and test dmesg log, kconfig, repro.c and repro binary are in link:
> > https://github.com/xupengfe/syzkaller_logs/tree/main/221103_152117_lwtunnel_valid_encap_type
> >
> > Kconfig, repro.c are in attached.
> >
> > If you fix this issue, thanks to add the Reported tag.
> >
> > Resend the email due to previous large attachment.
> 
> Thanks for the report.
> 
> A fix was submitted to the IPsec tree:
> https://lore.kernel.org/netdev/Y0UwqMZQ6n+G%2F%2FaD@shredder/
> 
  Ah, thanks for your information of fixed patch, please ignore this email.

  Thanks!
  BR.

> Thanks,
> Eyal.

      reply	other threads:[~2022-11-07  8:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07  3:27 Pengfei Xu
2022-11-07  6:09 ` Eyal Birger
2022-11-07  8:16   ` 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=Y2i+0N5zkwxmuyNO@xpf.sh.intel.com \
    --to=pengfei.xu@intel.com \
    --cc=eyal.birger@gmail.com \
    --cc=heng.su@intel.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

all inboxes | Powered by JetHome®