From: Jeff Garzik <jgarzik@pobox.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Tejun Heo <htejun@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: NV SATA breakage: jgarzik/libata-dev#upstream etc
Date: Sun, 24 Sep 2006 20:25:28 -0400 [thread overview]
Message-ID: <451721F8.4060600@pobox.com> (raw)
In-Reply-To: <m3wt7tm6sh.fsf@defiant.localdomain>
Krzysztof Halasa wrote:
> Hi,
>
> The following commit in libata-dev breaks NV SATA init - I don't
> have a dump handy, but the problem is a NULL ptr dereference here:
>
> libata-core.c
> int ata_device_add(const struct ata_probe_ent *ent)
> {
> ...
> /* register each port bound to this device */
> for (i = 0; i < host->n_ports; i++) {
> ...
> /* start port */
> rc = ap->ops->port_start(ap);
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> The problematic commit is fea63e38013ec628ab3f7fddc4c2148064b7910a:
> "[PATCH] libata: fix non-uniform ports handling
>
> Non-uniform ports handling got broken while updating libata to handle
> those in the same host. Only separate irq for the non-uniform
> secondary port was implemented while all other fields (host flags,
> transfer mode...) of the secondary port simply shared those of the
> first.
What's broken, and how does it affect NV sata?
That's the chipset on my main dev workstation, and there are no problems
here...
Jeff
next prev parent reply other threads:[~2006-09-25 0:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 18:57 NV SATA breakage: jgarzik/libata-dev#upstream etc Krzysztof Halasa
2006-09-25 0:25 ` Jeff Garzik [this message]
2006-09-25 12:51 ` Krzysztof Halasa
2006-09-25 17:15 ` Krzysztof Halasa
2006-09-25 22:20 ` Jeff Garzik
2006-09-25 23:50 ` Krzysztof Halasa
2006-09-25 23:52 ` Jeff Garzik
2006-09-26 0:29 ` Krzysztof Halasa
[not found] ` <1327be9e0609251112j34ccc787wbcc4886623af2714@mail.gmail.com>
2006-09-25 22:39 ` [PATCH v1] " Jeff Garzik
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=451721F8.4060600@pobox.com \
--to=jgarzik@pobox.com \
--cc=htejun@gmail.com \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.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 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.