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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 15 May 2008 18:23:19 -0400
From:	Tony Camuso <tcamuso@...hat.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	jbarnes@...tuousgeek.org, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org,
	"Schoeller, Patrick (Linux - Houston, TX)" <Patrick.Schoeller@...com>
Subject: Re: [PATCH] PCI: Correct last two HP entries in the bfsort whitelist

Alan Cox wrote:

> This is going to make everyone with those boxes who upgrades suddenely
> get their devices re-ordered and renamed when the probe order changes.
> That seems extremely inappropriate.
> 
> Alan

HP maintains that more of our customers, especially new customers,
will be adversely affected by NOT implementing this patch for the
following reasons.

1. HP issued a Customer Advisory for existing customers to use "pci=bfsort"
    in the boot command for these systems. Customers using pci=bfsort in
    their boot scripts will be unaffected by this patch.

2. Customers using only the two embedded NI devices will be unaffected.

3. Because of the use of labels for disk devices, they are unaffected.

4. New customers who must add pci=bfsort to their boot scripts have
    expressed dissatisfaction.

The only time this patch would induce any confusion for an existing customer
is upon the convergence of the following situations.

1. The user has not followed the instructions in the release notes
    for the DL360 and DL380,

    AND

2. The user has added NI cards to the option slots,

    AND

3. The user upgrades his kernel.



--
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/

Powered by blists - more mailing lists