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: <49CD46C8.8040606@msgid.tls.msk.ru>
Date:	Sat, 28 Mar 2009 00:36:08 +0300
From:	Michael Tokarev <mjt@....msk.ru>
To:	Jonathan Corbet <corbet@....net>
CC:	Dan Carpenter <error27@...il.com>, linux-kernel@...r.kernel.org,
	eteo@...hat.com
Subject: Re: [patch] char/raw.c locking on error

Jonathan Corbet wrote:
> (I bet raw doesn't need BKL at all; I'll see if I can't find some time
> to have a look later on).

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?

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