All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: syzbot <syzbot+bbc59256015533127d80@syzkaller.appspotmail.com>
Cc: gregkh@linuxfoundation.org,
	linux-kernel-mentees@lists.linuxfoundation.org,
	linux-kernel@vger.kernel.org, rafael@kernel.org,
	ricardo@marliere.net, skhan@linuxfoundation.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] general protection fault in serio_handle_event
Date: Fri, 20 Oct 2023 13:17:35 +0300	[thread overview]
Message-ID: <ZTJTv0hjVAgexanB@smile.fi.intel.com> (raw)
In-Reply-To: <000000000000701c7d06081bb14d@google.com>

On Thu, Oct 19, 2023 at 06:21:34PM -0700, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
> 
> commit fd6f7ad2fd4d53fa14f4fd190f9b05d043973892
> Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Date:   Mon Aug 28 14:58:24 2023 +0000
> 
>     driver core: return an error when dev_set_name() hasn't happened
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17a45b9d680000
> start commit:   65d6e954e378 Merge tag 'gfs2-v6.5-rc5-fixes' of git://git...
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=ff0db7a15ba54ead
> dashboard link: https://syzkaller.appspot.com/bug?extid=bbc59256015533127d80
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11d70614680000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=130eedb8680000
> 
> If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: driver core: return an error when dev_set_name() hasn't happened

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

-- 
With Best Regards,
Andy Shevchenko



WARNING: multiple messages have this Message-ID (diff)
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: syzbot <syzbot+bbc59256015533127d80@syzkaller.appspotmail.com>
Cc: rafael@kernel.org, syzkaller-bugs@googlegroups.com,
	linux-kernel@vger.kernel.org,
	linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [syzbot] [kernel?] general protection fault in serio_handle_event
Date: Fri, 20 Oct 2023 13:17:35 +0300	[thread overview]
Message-ID: <ZTJTv0hjVAgexanB@smile.fi.intel.com> (raw)
In-Reply-To: <000000000000701c7d06081bb14d@google.com>

On Thu, Oct 19, 2023 at 06:21:34PM -0700, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
> 
> commit fd6f7ad2fd4d53fa14f4fd190f9b05d043973892
> Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Date:   Mon Aug 28 14:58:24 2023 +0000
> 
>     driver core: return an error when dev_set_name() hasn't happened
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17a45b9d680000
> start commit:   65d6e954e378 Merge tag 'gfs2-v6.5-rc5-fixes' of git://git...
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=ff0db7a15ba54ead
> dashboard link: https://syzkaller.appspot.com/bug?extid=bbc59256015533127d80
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=11d70614680000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=130eedb8680000
> 
> If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: driver core: return an error when dev_set_name() hasn't happened

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

-- 
With Best Regards,
Andy Shevchenko


_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

  reply	other threads:[~2023-10-20 10:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08  8:46 [syzbot] [kernel?] general protection fault in serio_handle_event syzbot
2023-10-20  1:21 ` syzbot
2023-10-20  1:21   ` syzbot
2023-10-20 10:17   ` Andy Shevchenko [this message]
2023-10-20 10:17     ` Andy Shevchenko

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=ZTJTv0hjVAgexanB@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=ricardo@marliere.net \
    --cc=skhan@linuxfoundation.org \
    --cc=syzbot+bbc59256015533127d80@syzkaller.appspotmail.com \
    --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 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.