Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Kirill Tkhai <tkhai@yandex.ru>
To: Tejun Heo <tj@kernel.org>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] ata_port_wait_eh(): Change irqsave into unconditional closing of interrupts
Date: Thu, 26 Sep 2013 17:43:01 +0400	[thread overview]
Message-ID: <332301380202981@web24m.yandex.ru> (raw)
In-Reply-To: <20130926133153.GA2480@htj.dyndns.org>

26.09.2013, 17:32, "Tejun Heo" <tj@kernel.org>:
> Hello, Kirill.
>
> On Thu, Sep 26, 2013 at 05:21:19PM +0400, Kirill Tkhai wrote:
>
>>  Hi,
>>
>>  ata_port_wait_eh() uses spin_lock_irqsave() and this can confuse in fact
>>  that it is suitable to use in irqs_disabled() context. But we can't.
>>
>>  (schedule() returns with interrupts enabled so it's possible
>>  ata_port_wait_eh() enters with disabled interrupts but returns with enabled)
>>
>>  So, replace irqsave to unconditional closing of interrupts.
>>
>>  I propose to consider to add patch like this. (If you don't have a magic
>>  with flags which is not obvious for me :)
>
> Hmmm... yeah, this was Jeff's preference, at least way back, so libata
> has a lot of spin_lock_irqsave()'s where spin_lock_irq() should do.
> At this point, I don't really mind either way but if you wanna change
> it can you please do a full sweep through libata?  While I don't mind
> either state too much, I do want them to be mostly consistent one way
> or the other.

I don't exclude this, maybe, I do this in my spare time ;)

Kirill

      reply	other threads:[~2013-09-26 13:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26 13:21 [PATCH] ata_port_wait_eh(): Change irqsave into unconditional closing of interrupts Kirill Tkhai
2013-09-26 13:31 ` Tejun Heo
2013-09-26 13:43   ` Kirill Tkhai [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=332301380202981@web24m.yandex.ru \
    --to=tkhai@yandex.ru \
    --cc=linux-ide@vger.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