linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+953a33deaf38c66a915e@syzkaller.appspotmail.com>
To: benjamin.tissoires@redhat.com, dvyukov@google.com,
	hdanton@sina.com, jikos@kernel.org, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] general protection fault in hidraw_release
Date: Thu, 03 Feb 2022 22:00:17 -0800	[thread overview]
Message-ID: <0000000000000d8a7305d72af7f8@google.com> (raw)
In-Reply-To: <20220204054708.2335-1-hdanton@sina.com>

Hello,

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

Reported-and-tested-by: syzbot+953a33deaf38c66a915e@syzkaller.appspotmail.com

Tested on:

commit:         9f7fb8de Merge tag 'spi-fix-v5.17-rc2' of git://git.ke..
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
kernel config:  https://syzkaller.appspot.com/x/.config?x=b4a89edfcc8f7c74
dashboard link: https://syzkaller.appspot.com/bug?extid=953a33deaf38c66a915e
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: i386
patch:          https://syzkaller.appspot.com/x/patch.diff?x=1665d17c700000

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

  parent reply	other threads:[~2022-02-04  6:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220203102217.2229-1-hdanton@sina.com>
2022-02-03 12:18 ` [syzbot] general protection fault in hidraw_release syzbot
     [not found]   ` <20220204054708.2335-1-hdanton@sina.com>
2022-02-04  6:00     ` syzbot [this message]
2022-03-23 16:23     ` Jiri Kosina
2022-01-04  7:49 syzbot
2022-02-02  7:19 ` syzbot
     [not found]   ` <20220203040227.2057-1-hdanton@sina.com>
2022-02-03  6:09     ` Dmitry Vyukov
     [not found]       ` <20220203084246.2133-1-hdanton@sina.com>
2022-02-03  9:05         ` Dmitry Vyukov
2022-02-02 10:17 ` 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=0000000000000d8a7305d72af7f8@google.com \
    --to=syzbot+953a33deaf38c66a915e@syzkaller.appspotmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=dvyukov@google.com \
    --cc=hdanton@sina.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.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;
as well as URLs for NNTP newsgroup(s).