From: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Song Liu <songliubraving@fb.com>,
Kan Liang <kan.liang@linux.intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
syzkaller-bugs@googlegroups.com, Oleg Nesterov <oleg@redhat.com>
Subject: Re: Reminder: 22 open syzbot bugs in perf subsystem
Date: Wed, 3 Jul 2019 09:09:55 +0530 [thread overview]
Message-ID: <5a99f556-7449-55da-d901-0249352a5e15@linux.ibm.com> (raw)
In-Reply-To: <20190702054342.GB27702@sol.localdomain>
On 7/2/19 11:13 AM, Eric Biggers wrote:
> --------------------------------------------------------------------------------
> Title: possible deadlock in uprobe_clear_state
> Last occurred: 164 days ago
> Reported: 201 days ago
> Branches: Mainline
> Dashboard link: https://syzkaller.appspot.com/bug?id=a1ce9b3da349209c5085bb8c4fee753d68c3697f
> Original thread: https://lkml.kernel.org/lkml/00000000000010a9fb057cd14174@google.com/T/#u
>
> Unfortunately, this bug does not have a reproducer.
>
> No one replied to the original thread for this bug.
>
> If you fix this bug, please add the following tag to the commit:
> Reported-by: syzbot+1068f09c44d151250c33@syzkaller.appspotmail.com
>
> If you send any email or patch for this bug, please consider replying to the
> original thread. For the git send-email command to use, or tips on how to reply
> if the thread isn't in your mailbox, see the "Reply instructions" at
> https://lkml.kernel.org/r/00000000000010a9fb057cd14174@google.com
>
This is false positive:
https://marc.info/?l=linux-kernel&m=154925313012615&w=2
next prev parent reply other threads:[~2019-07-03 3:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 5:43 Eric Biggers
2019-07-03 3:39 ` Ravi Bangoria [this message]
2019-07-03 3:55 ` Eric Biggers
2019-07-03 3:59 ` Ravi Bangoria
2019-07-03 4:19 ` Eric Biggers
2019-07-03 4:36 ` Ravi Bangoria
2019-07-03 11:34 ` Oleg Nesterov
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=5a99f556-7449-55da-d901-0249352a5e15@linux.ibm.com \
--to=ravi.bangoria@linux.ibm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ebiggers@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®