All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian King <brking@linux.vnet.ibm.com>
To: Tejun Heo <tj@kernel.org>
Cc: Nishanth Aravamudan <nacc@us.ibm.com>,
	linuxppc-dev@lists.ozlabs.org, wayneb@linux.vnet.ibm.com,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	mbizon@freebox.fr, jgarzik@pobox.com
Subject: Re: libata/ipr/powerpc: regression between 2.6.39-rc4 and 2.6.39-rc5
Date: Thu, 16 Jun 2011 08:28:39 -0500	[thread overview]
Message-ID: <4DFA0507.3090609@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110616075114.GH8141@htj.dyndns.org>

On 06/16/2011 02:51 AM, Tejun Heo wrote:
> On Wed, Jun 15, 2011 at 04:34:17PM -0700, Nishanth Aravamudan wrote:
>>> That looks like the right thing to do. For ipr's usage of
>>> libata, we don't have the concept of a port frozen state, so this flag
>>> should really never get set. The alternate way to fix this would be to
>>> only set ATA_PFLAG_FROZEN in ata_port_alloc if ap->ops->error_handler
>>> is not NULL.
>>
>> It seemed like ipr is as you say, but I wasn't sure if it was
>> appropriate to make the change above in the common libata-scis code or
>> not. I don't want to break some other device on accident.
>>
>> Also, I tried your suggestion, but I don't think that can happen in
>> ata_port_alloc? ata_port_alloc is allocated ap itself, and it seems like
>> ap->ops typically gets set only after ata_port_alloc returns?
> 
> Maybe we can test error_handler in ata_sas_port_start()?

Good point. Since libsas is converted to the new eh now, we would need to have
this test.

Thanks,

Brian

-- 
Brian King
Linux on Power Virtualization
IBM Linux Technology Center



WARNING: multiple messages have this Message-ID (diff)
From: Brian King <brking@linux.vnet.ibm.com>
To: Tejun Heo <tj@kernel.org>
Cc: jgarzik@pobox.com, wayneb@linux.vnet.ibm.com,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	mbizon@freebox.fr, Nishanth Aravamudan <nacc@us.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: libata/ipr/powerpc: regression between 2.6.39-rc4 and 2.6.39-rc5
Date: Thu, 16 Jun 2011 08:28:39 -0500	[thread overview]
Message-ID: <4DFA0507.3090609@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110616075114.GH8141@htj.dyndns.org>

On 06/16/2011 02:51 AM, Tejun Heo wrote:
> On Wed, Jun 15, 2011 at 04:34:17PM -0700, Nishanth Aravamudan wrote:
>>> That looks like the right thing to do. For ipr's usage of
>>> libata, we don't have the concept of a port frozen state, so this flag
>>> should really never get set. The alternate way to fix this would be to
>>> only set ATA_PFLAG_FROZEN in ata_port_alloc if ap->ops->error_handler
>>> is not NULL.
>>
>> It seemed like ipr is as you say, but I wasn't sure if it was
>> appropriate to make the change above in the common libata-scis code or
>> not. I don't want to break some other device on accident.
>>
>> Also, I tried your suggestion, but I don't think that can happen in
>> ata_port_alloc? ata_port_alloc is allocated ap itself, and it seems like
>> ap->ops typically gets set only after ata_port_alloc returns?
> 
> Maybe we can test error_handler in ata_sas_port_start()?

Good point. Since libsas is converted to the new eh now, we would need to have
this test.

Thanks,

Brian

-- 
Brian King
Linux on Power Virtualization
IBM Linux Technology Center

  reply	other threads:[~2011-06-16 13:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15 19:17 libata/ipr/powerpc: regression between 2.6.39-rc4 and 2.6.39-rc5 Nishanth Aravamudan
2011-06-15 19:17 ` Nishanth Aravamudan
2011-06-15 20:02 ` Brian King
2011-06-15 20:02   ` Brian King
2011-06-15 23:34   ` Nishanth Aravamudan
2011-06-15 23:34     ` Nishanth Aravamudan
2011-06-16  7:51     ` Tejun Heo
2011-06-16  7:51       ` Tejun Heo
2011-06-16 13:28       ` Brian King [this message]
2011-06-16 13:28         ` Brian King
2011-06-16 15:28         ` [PATCH] libata/sas: only set FROZEN flag if new EH is supported Nishanth Aravamudan
2011-06-16 15:28           ` Nishanth Aravamudan
2011-06-21 16:07           ` Nishanth Aravamudan
2011-06-21 16:07             ` Nishanth Aravamudan
2011-06-21 20:30             ` Brian King
2011-06-21 20:30               ` Brian King
2011-06-21 20:39               ` Jeff Garzik
2011-06-21 20:39                 ` Jeff Garzik
2011-06-23  4:31               ` Benjamin Herrenschmidt
2011-06-23  4:31                 ` Benjamin Herrenschmidt
2011-06-23  4:42                 ` Benjamin Herrenschmidt
2011-06-23  4:42                   ` Benjamin Herrenschmidt
2011-06-23  5:10                   ` Benjamin Herrenschmidt
2011-06-23  5:10                     ` Benjamin Herrenschmidt
2011-06-23 17:15                   ` Nishanth Aravamudan
2011-06-23 17:15                     ` Nishanth Aravamudan
2011-06-23 20:05                     ` Brian King
2011-06-23 20:05                       ` Brian King
2011-06-23 20:05                       ` Brian King
2011-06-23 21:43                       ` Benjamin Herrenschmidt
2011-06-23 21:43                         ` Benjamin Herrenschmidt

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=4DFA0507.3090609@linux.vnet.ibm.com \
    --to=brking@linux.vnet.ibm.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mbizon@freebox.fr \
    --cc=nacc@us.ibm.com \
    --cc=tj@kernel.org \
    --cc=wayneb@linux.vnet.ibm.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 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.