public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8e67d6db6ac1d1b297f7@syzkaller.appspotmail.com>
To: davem@davemloft.net, jiri@nvidia.com, kuba@kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING: fbcon: Driver 'vkmclient_loop: send disconnect: Broken pipe
Date: Thu, 09 Mar 2023 10:13:29 -0800	[thread overview]
Message-ID: <000000000000068c2505f67b9a8d@google.com> (raw)
In-Reply-To: <0000000000008fb52f05eb515c2d@google.com>

syzbot suspects this issue was fixed by commit:

commit ed539ba614a079ea696b92beef1eafec66f831a4
Author: Jakub Kicinski <kuba@kernel.org>
Date:   Fri Jan 6 06:33:57 2023 +0000

    devlink: always check if the devlink instance is registered

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=13f213eac80000
start commit:   55be6084c8e0 Merge tag 'timers-core-2022-10-05' of git://g..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=c29b6436e994d72e
dashboard link: https://syzkaller.appspot.com/bug?extid=8e67d6db6ac1d1b297f7
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=172e57a4880000

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

#syz fix: devlink: always check if the devlink instance is registered

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

      reply	other threads:[~2023-03-09 18:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 16:12 [syzbot] WARNING: fbcon: Driver 'vkmclient_loop: send disconnect: Broken pipe syzbot
2023-03-09 18:13 ` syzbot [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=000000000000068c2505f67b9a8d@google.com \
    --to=syzbot+8e67d6db6ac1d1b297f7@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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