linux-kernel - Re: [PATCH, RFC] Char dev BKL pushdown v2

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: <aday7665469.fsf@cisco.com>
Date:	Mon, 19 May 2008 15:18:06 -0700
From:	Roland Dreier <rdreier@...co.com>
To:	corbet@....net (Jonathan Corbet)
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Alexander Viro <viro@....linux.org.uk>,
	linux-kernel@...r.kernel.org,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH, RFC] Char dev BKL pushdown v2

 > That's part of it, but, as Alan pointed out, there's more.  The BKL
 > currently protects open() calls against concurrency with other opens,
 > with ioctl(), and with driver initialization as well.  So it's a matter
 > of having one's locking and ordering act together in general.

Thanks.  Just to be super-explicit, ioctl() cannot be called on a given
file until the open() for that particular file has returned, right?

And the point about driver initialization is that open() can be called
as soon as the file operations are registered, even if the module_init
function has not returned?

Thanks,
  Roland
--
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/