public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+60df062e1c41940cae0f@syzkaller.appspotmail.com>
To: dri-devel@lists.freedesktop.org, fmdefrancesco@gmail.com,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in component_del
Date: Tue, 08 Feb 2022 06:51:07 -0800	[thread overview]
Message-ID: <000000000000e03f4e05d782d886@google.com> (raw)
In-Reply-To: <2114181.C4sosBPzcN@leap>

Hello,

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

Reported-and-tested-by: syzbot+60df062e1c41940cae0f@syzkaller.appspotmail.com

Tested on:

commit:         555f3d7b Merge tag '5.17-rc3-ksmbd-server-fixes' of gi..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=266de9da75c71a45
dashboard link: https://syzkaller.appspot.com/bug?extid=60df062e1c41940cae0f
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch:          https://syzkaller.appspot.com/x/patch.diff?x=111f7428700000

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

  reply	other threads:[~2022-02-08 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 22:36 [syzbot] WARNING in component_del syzbot
2022-02-08  7:51 ` syzbot
2022-02-08 12:30   ` Daniel Vetter
2022-02-08 12:39     ` Pavel Skripkin
2022-02-08 14:38   ` Fabio M. De Francesco
2022-02-08 14:51     ` syzbot [this message]
2022-02-08 10:37 ` syzbot
2022-02-09 13:42   ` Heikki Krogerus
2022-02-09 13:51     ` Pavel Skripkin
2022-02-09 13:56       ` Heikki Krogerus

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=000000000000e03f4e05d782d886@google.com \
    --to=syzbot+60df062e1c41940cae0f@syzkaller.appspotmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fmdefrancesco@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@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