linux-kernel - Re: [PATCH] libata: fix combined mode (was Re: Happy New Year (and v2.6.20-rc3 released))

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 2 Jan 2007 21:27:01 +0000
From:	Alan <alan@...rguk.ukuu.org.uk>
To:	Jeff Garzik <jgarzik@...ox.com>
Cc:	Linus Torvalds <torvalds@...l.org>,
	Alessandro Suardi <alessandro.suardi@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] libata: fix combined mode (was Re: Happy New Year (and
 v2.6.20-rc3 released))

> > This is a silly complaint because the SFF layer in libata doesn't handle
> > this case yet anyway.
> 
> Yes, it's "silly" people people use configurations you find inconvenient.
> 
> At least one embedded x86 case cares, that I know of.  They only needed 
> to make two minor changes to make it work.

*It is not part of 2.6.20*

> The code no long reserves resources for the "extra" PCI BAR that often 
> exists on PCI controllers regardless of legacy/native mode.  Previously, 
> the code called pci_request_regions() to reserve ALL regions attached to 
> the PCI device.

We use BAR5 on two devices in legacy mode. Both of those reserve all the
other resources. We can fix BAR5 in .21 when all the combined mode crap
goes away.

> You have suddenly decided that it's OK to --not reserve at all-- these 
> additional regions.

It's not ideal - but it is perfectly sufficient for 2.6.20

> Proof:  The AHCI PCI BAR (#5, zero-based) is clearly NOT reserved, even 
> though we talk to it, in piix_disable_ahci() of ata_piix.c.

We always claim the other BARs so catch a collision.

Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/