All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+36edb5cac286af8e3385@syzkaller.appspotmail.com>
To: avagin@virtuozzo.com, davem@davemloft.net, dvyukov@google.com,
	jon.maloy@ericsson.com, keescook@chromium.org,
	ktkhai@virtuozzo.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, nicolas.dichtel@6wind.com,
	syzkaller-bugs@googlegroups.com,
	tipc-discussion@lists.sourceforge.net, xiyou.wangcong@gmail.com,
	ying.xue@windriver.com
Subject: Re: INFO: task hung in ctrl_getfamily
Date: Mon, 14 Sep 2020 03:43:07 -0700	[thread overview]
Message-ID: <00000000000031842b05af43b363@google.com> (raw)
In-Reply-To: <000000000000eb3fa9057cbc2f06@google.com>

syzbot suspects this issue was fixed by commit:

commit 47733f9daf4fe4f7e0eb9e273f21ad3a19130487
Author: Cong Wang <xiyou.wangcong@gmail.com>
Date:   Sat Aug 15 23:29:15 2020 +0000

    tipc: fix uninit skb->data in tipc_nl_compat_dumpit()

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13f287b3900000
start commit:   f5d58277 Merge branch 'for-linus' of git://git.kernel.org/..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=c8970c89a0efbb23
dashboard link: https://syzkaller.appspot.com/bug?extid=36edb5cac286af8e3385
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=139f101b400000

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

#syz fix: tipc: fix uninit skb->data in tipc_nl_compat_dumpit()

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

  parent reply	other threads:[~2020-09-14 10:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 10:03 INFO: task hung in ctrl_getfamily syzbot
2018-12-11 10:04 ` Dmitry Vyukov
2019-03-24 15:44 ` syzbot
2020-09-14 10:43 ` syzbot [this message]
2020-11-11 13:56   ` Dmitry Vyukov

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=00000000000031842b05af43b363@google.com \
    --to=syzbot+36edb5cac286af8e3385@syzkaller.appspotmail.com \
    --cc=avagin@virtuozzo.com \
    --cc=davem@davemloft.net \
    --cc=dvyukov@google.com \
    --cc=jon.maloy@ericsson.com \
    --cc=keescook@chromium.org \
    --cc=ktkhai@virtuozzo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=xiyou.wangcong@gmail.com \
    --cc=ying.xue@windriver.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 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.