linux-kernel - Re: Regression? 2.6.23.16 -> 2.6.32.9: ide/libata HD recognition

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] [day] [month] [year] [list]

Date:	Sat, 13 Mar 2010 18:39:58 +1100
From:	CaT <cat@....com.au>
To:	Robert Hancock <hancockrwd@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Regression? 2.6.23.16 -> 2.6.32.9: ide/libata HD recognition

On Thu, Mar 11, 2010 at 06:04:38PM -0600, Robert Hancock wrote:
> That sounds like you had a slave with no master on the second IDE  

Indeed.

> channel. That really isn't a wise configuration and is prone to break  
> (some devices don't work in this setup, some BIOSes choke, etc.) since  
> the standard doesn't really allow this (the spec says that support for  
> this configuration is "host specific" and not mandatory).

I've never had it cause issues. BIOS has always recognised the HDs and
linux, until now, has always been more than happy to work with them.
This is across many different mbs, ide chips and hds.

On this server a lone hdd has been the case for 4 years and has worked
fine.

> Essentially, fixing the hardware config to set the drive for master if  
> it's the only device on the channel is likely the best solution overall.

It is what worked, after a lot of futzing around. Still, this is a
regression (from the pov of someone who just had to futz). Before
whatever change was made things were fine and futz-free.

-- 
  "A search of his car uncovered pornography, a homemade sex aid, women's 
  stockings and a Jack Russell terrier."
    - http://www.news.com.au/story/0%2C27574%2C24675808-421%2C00.html
--
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/