From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-mm@kvack.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: [Bugme-new] [Bug 16321] New: os unresponsive during buffered I/O
Date: Tue, 20 Jul 2010 10:50:52 -0700 [thread overview]
Message-ID: <20100720105052.e077be1c.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100720150855.GA17832@infradead.org>
On Tue, 20 Jul 2010 11:08:55 -0400 Christoph Hellwig <hch@infradead.org> wrote:
> On Mon, Jul 19, 2010 at 09:10:36PM -0700, Andrew Morton wrote:
> > The reporter has updated the report, says "This bug is consistently
> > reproducible.". But no signs of interest from kernel developers yet.
>
> If only the reported can reproduce it that doesn't really help anyone.
Garbage. We have a reporter who is prepared to work with us. Has
anyone tried talking him through using the relevant tracepoints?
Sending patches to add new ones if needed?
> And neither does hiding bugreports in bugzilla help when this could be
> discussed much more usefully on the list.
The guy's email address is right there. And there are over forty more
people at https://bugzilla.kernel.org/show_bug.cgi?id=7372 seeing
similar (or other!) problems.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2010-07-20 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16321-10286@https.bugzilla.kernel.org/>
2010-07-02 23:05 ` [Bugme-new] [Bug 16321] New: os unresponsive during buffered I/O Andrew Morton
2010-07-03 11:56 ` Jens Axboe
2010-07-03 15:16 ` Andrew Morton
2010-07-03 19:55 ` Avi Kivity
2010-07-20 4:10 ` Andrew Morton
2010-07-20 15:08 ` Christoph Hellwig
2010-07-20 17:50 ` Andrew Morton [this message]
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=20100720105052.e077be1c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-mm@kvack.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 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).