All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: linux-kernel@vger.kernel.org, carns@mcs.anl.gov
Subject: Re: [patch] cfq: Don't allow queue merges for queues that have no process references
Date: Thu, 17 Jun 2010 20:15:52 +0200	[thread overview]
Message-ID: <4C1A6658.1070704@kernel.dk> (raw)
In-Reply-To: <x49ocf9agio.fsf@segfault.boston.devel.redhat.com>

On 2010-06-17 16:19, Jeff Moyer wrote:
> Hi,
> 
> A user reported a kernel bug when running a particular program that did
> the following
> 
> created 32 threads
> - each thread took a mutex, grabbed a global offset, added a buffer size
>   to that offset, released the lock
> - read from the given offset in the file
> - created a new thread to do the same
> - exited

[snip]

Thanks for doing the excellent writeup and nailing this bug, I'll commit
it and mark it for -stable.

-- 
Jens Axboe


      reply	other threads:[~2010-06-17 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17 14:19 [patch] cfq: Don't allow queue merges for queues that have no process references Jeff Moyer
2010-06-17 18:15 ` Jens Axboe [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=4C1A6658.1070704@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=carns@mcs.anl.gov \
    --cc=jmoyer@redhat.com \
    --cc=linux-kernel@vger.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.