All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+a172213a651850d94cf2@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, jslaby@suse.com, jslaby@suse.cz,
	linux-kernel@vger.kernel.org, okash.khawaja@gmail.com,
	samuel.thibault@ens-lyon.org, syzkaller-bugs@googlegroups.com
Subject: Re: INFO: task hung in paste_selection
Date: Mon, 16 Mar 2020 13:37:04 -0700	[thread overview]
Message-ID: <0000000000003a06e005a0fec8cc@google.com> (raw)
In-Reply-To: <0000000000003a2af3059905d1dc@google.com>

syzbot suspects this bug was fixed by commit:

commit e8c75a30a23c6ba63f4ef6895cbf41fd42f21aa2
Author: Jiri Slaby <jslaby@suse.cz>
Date:   Fri Feb 28 11:54:06 2020 +0000

    vt: selection, push sel_lock up

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=14aada1de00000
start commit:   ae4b064e Merge tag 'afs-fixes-20191211' of git://git.kerne..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=79f79de2a27d3e3d
dashboard link: https://syzkaller.appspot.com/bug?extid=a172213a651850d94cf2
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=13bf312ee00000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=116cce46e00000

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

#syz fix: vt: selection, push sel_lock up

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

  parent reply	other threads:[~2020-03-16 20:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06  9:39 INFO: task hung in paste_selection syzbot
2019-12-12  9:32 ` syzbot
2020-03-16 20:37 ` syzbot [this message]
2020-03-17  5:59   ` Jiri Slaby

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=0000000000003a06e005a0fec8cc@google.com \
    --to=syzbot+a172213a651850d94cf2@syzkaller.appspotmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=okash.khawaja@gmail.com \
    --cc=samuel.thibault@ens-lyon.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 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.