From: Ted Ts'o <tytso@mit.edu>
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
sandeen@redhat.com, adilger@dilger.ca
Subject: Re: [PATCH] ext4: Fix lazyinit hang after removing request
Date: Tue, 2 Nov 2010 14:20:23 -0400 [thread overview]
Message-ID: <20101102182023.GD25614@thunk.org> (raw)
In-Reply-To: <1288358420-11643-1-git-send-email-lczerner@redhat.com>
On Fri, Oct 29, 2010 at 03:20:20PM +0200, Lukas Czerner wrote:
> When the request has been removed from the list and no other request
> has been issued, we will end up with next wakeup scheduled to
> MAX_JIFFY_OFFSET which is bad. So check for that.
>
> Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Queued for pushing to Linus for 2.6.27-rc2, thanks.
- Ted
prev parent reply other threads:[~2010-11-02 18:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 13:20 [PATCH] ext4: Fix lazyinit hang after removing request Lukas Czerner
2010-11-02 18:20 ` Ted Ts'o [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=20101102182023.GD25614@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).