linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+9cd5837a045bbee5b810@syzkaller.appspotmail.com>
To: clang-built-linux@googlegroups.com, davem@davemloft.net,
	herbert@gondor.apana.org.au, kbuild-all@lists.01.org,
	kuba@kernel.org, linux-kernel@vger.kernel.org, lkp@intel.com,
	netdev@vger.kernel.org, paskripkin@gmail.com,
	steffen.klassert@secunet.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] UBSAN: shift-out-of-bounds in xfrm_set_default
Date: Tue, 27 Jul 2021 17:13:10 -0700	[thread overview]
Message-ID: <00000000000009346505c823da46@google.com> (raw)
In-Reply-To: <20210727203056.377e5758@gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+9cd5837a045bbee5b810@syzkaller.appspotmail.com

Tested on:

commit:         42d0b5f5 Add linux-next specific files for 20210727
git tree:       linux-next
kernel config:  https://syzkaller.appspot.com/x/.config?x=e5bd567a6f50f462
dashboard link: https://syzkaller.appspot.com/bug?extid=9cd5837a045bbee5b810
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1204e0dc300000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2021-07-28  0:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 12:47 [syzbot] UBSAN: shift-out-of-bounds in xfrm_set_default syzbot
2021-07-27 14:43 ` Pavel Skripkin
2021-07-27 17:25   ` [PATCH] net: xfrm: fix shift-out-of-bounce kernel test robot
2021-07-27 17:30     ` Pavel Skripkin
2021-07-28  0:13       ` syzbot [this message]
2021-07-27 17:46   ` kernel test robot
2021-07-27 23:28   ` [syzbot] UBSAN: shift-out-of-bounds in xfrm_set_default syzbot

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=00000000000009346505c823da46@google.com \
    --to=syzbot+9cd5837a045bbee5b810@syzkaller.appspotmail.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kbuild-all@lists.01.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=paskripkin@gmail.com \
    --cc=steffen.klassert@secunet.com \
    --cc=syzkaller-bugs@googlegroups.com \
    /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;
as well as URLs for NNTP newsgroup(s).