linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+68dce7caebd8543121de@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, ast@kernel.org, boqun.feng@gmail.com,
	byungchul.park@lge.com, daniel@iogearbox.net,
	davem@davemloft.net, dledford@redhat.com, jgg@mellanox.com,
	jgg@ziepe.ca, kernel-team@lge.com, kirill@shutemov.name,
	kuznet@ms2.inr.ac.ru, leon@kernel.org, leonro@mellanox.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-rdma@vger.kernel.org, mingo@kernel.org,
	netdev@vger.kernel.org, npiggin@gmail.com, parav@mellanox.com,
	peterz@infradead.org, syzkaller-bugs@googlegroups.com,
	tglx@linutronix.de, torvalds@linux-foundation.org,
	walken@google.com, willy@infradead.org, yoshfuji@linux-ipv6.org
Subject: Re: KASAN: slab-out-of-bounds Read in ip6_tnl_parse_tlv_enc_lim
Date: Tue, 10 Dec 2019 14:08:01 -0800	[thread overview]
Message-ID: <000000000000e22b3c059960bebd@google.com> (raw)
In-Reply-To: <0000000000005175bf057617c71d@google.com>

syzbot suspects this bug was fixed by commit:

commit 30471d4b20335d9bd9ae9b2382a1e1e97d18d86d
Author: Leon Romanovsky <leonro@mellanox.com>
Date:   Sun Feb 3 12:55:50 2019 +0000

     RDMA/core: Share driver structure size with core

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=16b7bb7ae00000
start commit:   3a5af36b Merge tag '4.19-rc3-smb3-cifs' of git://git.samba..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=9c4a80625153107e
dashboard link: https://syzkaller.appspot.com/bug?extid=68dce7caebd8543121de
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1068a44e400000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=146386c6400000

If the result looks correct, please mark the bug fixed by replying with:

#syz fix: RDMA/core: Share driver structure size with core

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

       reply	other threads:[~2019-12-10 22:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0000000000005175bf057617c71d@google.com>
2019-12-10 22:08 ` syzbot [this message]
2019-12-10 22:11   ` KASAN: slab-out-of-bounds Read in ip6_tnl_parse_tlv_enc_lim Jason Gunthorpe

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=000000000000e22b3c059960bebd@google.com \
    --to=syzbot+68dce7caebd8543121de@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ast@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=byungchul.park@lge.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dledford@redhat.com \
    --cc=jgg@mellanox.com \
    --cc=jgg@ziepe.ca \
    --cc=kernel-team@lge.com \
    --cc=kirill@shutemov.name \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=leon@kernel.org \
    --cc=leonro@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=npiggin@gmail.com \
    --cc=parav@mellanox.com \
    --cc=peterz@infradead.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=walken@google.com \
    --cc=willy@infradead.org \
    --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 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).