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

Message-Id: <E1LnLnk-0002B1-5Y@be1.7eggert.dyndns.org>
Date:	Sat, 28 Mar 2009 00:49:27 +0100
From:	Bodo Eggert <7eggert@....de>
To:	Jonathan Corbet <corbet@....net>, Michael Tokarev <mjt@....msk.ru>,
	Dan Carpenter <error27@...il.com>,
	linux-kernel@...r.kernel.org, eteo@...hat.com
Subject: Re: [patch] char/raw.c locking on error

Jonathan Corbet <corbet@....net> wrote:
> 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?

As long as you don't fix all the legacy applications to use O_DIRECT.

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

It had long been done when before it was discussed the last time.

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