linux-kernel - Re: [patch] char/raw.c locking on error

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: <20090327154403.4712afe3@bike.lwn.net>
Date:	Fri, 27 Mar 2009 15:44:03 -0600
From:	Jonathan Corbet <corbet@....net>
To:	Michael Tokarev <mjt@....msk.ru>
Cc:	Dan Carpenter <error27@...il.com>, linux-kernel@...r.kernel.org,
	eteo@...hat.com
Subject: Re: [patch] char/raw.c locking on error

On Sat, 28 Mar 2009 00:36:08 +0300
Michael Tokarev <mjt@....msk.ru> wrote:

> Is it still in use - the raw driver, that is?  Nowadays,
> every block device can be opened in direct mode by using
> O_DIRECT - this is what raw does.  I mean, is it worth
> spending even more time on it?

This was discussed a while back.  My understanding is that there are
people using it.  It is a user-space ABI of sorts which can't just be
yanked arbitrarily.  The right thing to do is probably to replace it
with a shell implementation that just opens the device using O_DIRECT,
but nobody has actually done that...

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