From: ejun Heo <tj@kernel.org>
To: viresh kumar <viresh.linux@gmail.com>
Cc: Viresh Kumar <viresh.kumar@st.com>,
jgarzik@pobox.com, linux-ide@vger.kernel.org,
shiraz.hashim@st.com, armando.visconti@st.com, amit.goel@st.com
Subject: Re: [PATCH V2 2/2] pata_arasan_cf: Adding support for arasan compact flash host controller
Date: Fri, 18 Feb 2011 18:20:52 +0100 [thread overview]
Message-ID: <20110218172052.GT21209@htj.dyndns.org> (raw)
In-Reply-To: <AANLkTi=bK54_OEFh=Fhx9N8TxVcFxUFYJm8XS=MKZdG2@mail.gmail.com>
Hello,
On Fri, Feb 18, 2011 at 10:28:51PM +0530, viresh kumar wrote:
> > Hmmm... so, now there's a work item which requeues itself. That can't
> > be reliably stopped from freeze() as it's called with host lock held
> > without process context. I think you should override
> > ->error_handler() which looks like the following,
>
> actually i am disabling controller in freeze. After which we will
> surely get timeout here and
> so finally we will get an error in this work. Wouldn't that be enough?
Hmmm... libata usually invokes EH right away after freeze(). It'll
abort everything in flight and wake up the EH. freeze()'s job is to
_try_ to quiesce the controller until reset and used when libata isn't
sure which state the port is in, so I think you would still need to
kill the work items on entry to EH. BTW, have you tested the EH
paths? Inducing fake failures from interrupt handler and let things
just slide so that timeout happens should do the trick.
Thanks.
--
tejun
next prev parent reply other threads:[~2011-02-18 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 11:40 [PATCH V2 0/2] add pata_arasan_cf support Viresh Kumar
2011-02-18 11:40 ` [PATCH V1 1/2] libata-sff: add ata_sff_queue_work() & ata_sff_queue_delayed_work() Viresh Kumar
2011-02-18 14:11 ` Tejun Heo
2011-02-18 11:40 ` [PATCH V2 2/2] pata_arasan_cf: Adding support for arasan compact flash host controller Viresh Kumar
2011-02-18 14:34 ` Tejun Heo
2011-02-18 16:58 ` viresh kumar
2011-02-18 17:20 ` ejun Heo [this message]
2011-02-19 3:39 ` viresh kumar
2011-02-21 8:31 ` Tejun Heo
2011-02-22 5:46 ` viresh kumar
2011-02-22 8:58 ` Tejun Heo
2011-02-22 7:03 ` viresh kumar
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=20110218172052.GT21209@htj.dyndns.org \
--to=tj@kernel.org \
--cc=amit.goel@st.com \
--cc=armando.visconti@st.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=shiraz.hashim@st.com \
--cc=viresh.kumar@st.com \
--cc=viresh.linux@gmail.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).