linux-kernel - Re: What still uses the block layer?

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]

Message-ID: <47151C8B.5050704@s5r6.in-berlin.de>
Date:	Tue, 16 Oct 2007 22:18:19 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Matthew Wilcox <matthew@....cx>
CC:	david@...g.hm, Alan Cox <alan@...rguk.ukuu.org.uk>,
	Rob Landley <rob@...dley.net>,
	David Newall <david@...idnewall.com>,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
	Suparna Bhattacharya <suparna@...ibm.com>,
	Nick Piggin <piggin@...erone.com.au>
Subject: Re: What still uses the block layer?

Matthew Wilcox wrote:
> On Tue, Oct 16, 2007 at 12:54:58PM -0700, david@...g.hm wrote:
>> On Tue, 16 Oct 2007, Alan Cox wrote:
>>> I wouldn't try dividing those by pata v sata. You'll cause all sorts of
>>> problems in the process because of PATA-SATA and SATA-PATA bridges.
>> if you use a PATA-SATA bridge (IDE drive SATA controller), it would look 
>> to the system like a SATA drive and be addressed and enumerated as SATA.
> 
> But you don't know where the bridge is.  It might be on the drive's
> board, it might be an explicit enclosure, or it might be on the
> motherboard.  Each of those scenarios is going to have a different user
> expectation.

If the bridge is on the drive's board or in an enclosure, the user's
expectations are fully met.

If the bridge is on the motherboard, then the user may be surprised
unless he knows the motherboard well enough.

But this is _far_ less of an issue than
  - the hda<->sda confusion,
  - the confusion caused by all kernel default names put into a single
    namespace.

I don't have a personal interest in PATA/SATA distinction though.  I
suppose once PATA went into the SCSI namespace and then this namespace
is divided again, it's not a big issue anymore whether PATA and SATA
share an ATA namespace or are distinct, except perhaps for people with
IDE drive and eSATA slots.
-- 
Stefan Richter
-=====-=-=== =-=- =----
http://arcgraph.de/sr/
-
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/