All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
	syzkaller-bugs@googlegroups.com, jeffv@google.com
Subject: Re: Reminder: 5 open syzbot bugs in lockdep subsystem
Date: Wed, 10 Jul 2019 07:14:10 -0700	[thread overview]
Message-ID: <f614ac47-34c3-fac4-c096-fd835ce6d35a@acm.org> (raw)
In-Reply-To: <20190710055838.GC2152@sol.localdomain>

On 7/9/19 10:58 PM, Eric Biggers wrote:
> [This email was generated by a script.  Let me know if you have any suggestions
> to make it better, or if you want it re-generated with the latest status.]
> 
> Of the currently open syzbot reports against the upstream kernel, I've manually
> marked 5 of them as possibly being bugs in the lockdep subsystem.  I've listed
> these reports below, sorted by an algorithm that tries to list first the reports
> most likely to be still valid, important, and actionable.
> 
> Of these 5 bugs, 3 were seen in mainline in the last week.
> 
> Of these 5 bugs, 1 was bisected to a commit from the following person:
> 
> 	Bart Van Assche <bvanassche@acm.org>

(+jeffv)

Hi Eric,

Several days ago I had already explained to you that the bisection 
result that led to one of my commits did not make any sense to me. So I 
do not appreciate this kind of fingerpointing. Please stop doing this.

Bart.

  reply	other threads:[~2019-07-10 14:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10  5:58 Reminder: 5 open syzbot bugs in lockdep subsystem Eric Biggers
2019-07-10 14:14 ` Bart Van Assche [this message]
2019-07-10 16:13   ` Eric Biggers

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=f614ac47-34c3-fac4-c096-fd835ce6d35a@acm.org \
    --to=bvanassche@acm.org \
    --cc=jeffv@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=will@kernel.org \
    /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.