From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Shane Huang <Shane.Huang@amd.com>,
stable@kernel.org
Subject: Re: [PATCH #upstream-fixes UPDATED] libata: fix last_reset timestamp handling
Date: Tue, 11 Nov 2008 03:02:07 -0500 [thread overview]
Message-ID: <49193BFF.2000401@garzik.org> (raw)
In-Reply-To: <49100308.90207@kernel.org>
Tejun Heo wrote:
> ehc->last_reset is used to ensure that resets are not issued too close
> to each other. It's initialized to jiffies minus one minute on EH
> entry. However, when new links are initialized after PMP is probed,
> new links have zero for this timestamp resulting in long wait
> depending on the current jiffies.
>
> This patch makes last_set considered iff ATA_EHI_DID_RESET is set, in
> which case last_reset is always initialized. As an added precaution,
> WARN_ON() is added so that warning is printed if last_reset is in
> future.
>
> This problem is spotted and debugged by Shane Huang.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Cc: Shane Huang <Shane.Huang@amd.com>
> ---
> This one also should go into 2.6.27-x. Thanks.
>
> Minor update. Kill ehc->last_reset update right after
> ata_eh_about_to_do(). This does no harm but is unnecessary with the
> patch applied.
>
> drivers/ata/libata-eh.c | 21 +++++++++++----------
> 1 file changed, 11 insertions(+), 10 deletions(-)
applied
prev parent reply other threads:[~2008-11-11 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 7:32 [PATCH #upstream-fixes] libata: fix last_reset timestamp handling Tejun Heo
2008-11-04 8:08 ` [PATCH #upstream-fixes UPDATED] " Tejun Heo
2008-11-11 8:02 ` Jeff Garzik [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=49193BFF.2000401@garzik.org \
--to=jeff@garzik.org \
--cc=Shane.Huang@amd.com \
--cc=linux-ide@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tj@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 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).