From: Andrey Kalachev <kalachev@swemel.ru>
To: Michal Switala <michal.switala@infogain.com>
Cc: davem@davemloft.net, kuba@kernel.org, kuznet@ms2.inr.ac.ru,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzbot+e738404dcd14b620923c@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com, yoshfuji@linux-ipv6.org,
lvc-project@linuxtesting.org
Subject: Re: Progress in ticket
Date: Thu, 27 Jun 2024 18:55:15 +0300 [thread overview]
Message-ID: <Zn2LY7gGod2J4UpH@ural> (raw)
In-Reply-To: <20240627115544.1090671-1-michal.switala@infogain.com>
On Thu, Jun 27, 2024 at 01:55:44PM +0200, Michal Switala wrote:
>Hello,
>
>I am currently looking at this bug and checked your reproduction.
>Unfortunately, it doesn's set xfrm transformations in the same way as
>syz reproducer. The effect is that in xfrm_lookup_with_ifid, the packet goes to
>the nopol section instead of notransform as in the original.
>
>Regards
>Michal
Hi Michal.
Most likely system("ip xfrm policy update src 254.136.0.0/0 dst 255.1.0.0/0 dir out flag icmp") does not work.
syzkaller uses Busybox based disk images.
ip is present there (/sbin/ip), but it has limited functionality.
In particular, the xfrm framework commands are not supported.
The original reproducer worked with ipsec/xfrm via netlink.
The rewritten reproducer will work with a Debian-based image with iproute2 installed.
I made a Debian image of bullseye (the easiest way to do that is to use create-image.sh).
Regards,
Andrey
prev parent reply other threads:[~2024-06-27 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 18:26 [syzbot] WARNING in ip_rt_bug (2) syzbot
2024-06-21 14:45 ` Andrey Kalachev
2024-06-27 11:55 ` Progress in ticket Michal Switala
2024-06-27 15:55 ` Andrey Kalachev [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=Zn2LY7gGod2J4UpH@ural \
--to=kalachev@swemel.ru \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=michal.switala@infogain.com \
--cc=netdev@vger.kernel.org \
--cc=syzbot+e738404dcd14b620923c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yoshfuji@linux-ipv6.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.