Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <Y2h7PgIkraOI1zVC@xpf.sh.intel.com>
In-Reply-To: <Y2h7PgIkraOI1zVC@xpf.sh.intel.com>
From:   Eyal Birger <eyal.birger@gmail.com>
Date:   Mon, 7 Nov 2022 08:09:39 +0200
Message-ID: <CAHsH6Gt92EH7eC5MyL23G7ySYk4OyNoC9U=0Y7vXbbqVyyZ7SQ@mail.gmail.com>
Subject: Re: [syzkaller] There is "lwtunnel_valid_encap_type" WARNING in
 6.1-rc3 mainline kernel
To:     Pengfei Xu <pengfei.xu@intel.com>
Cc:     linux-kernel@vger.kernel.org, heng.su@intel.com
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

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/

Thanks,
Eyal.