linux-kernel - Re: [PATCH 2/2] uio: do not expose inode to uio open/release hooks

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: <20121211232032.GA24933@kroah.com>
Date:	Tue, 11 Dec 2012 15:20:32 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Benedikt Spranger <b.spranger@...utronix.de>
Cc:	linux-kernel@...r.kernel.org, hjk@...sjkoch.de,
	Alexander.Frank@...rspaecher.com
Subject: Re: [PATCH 2/2] uio: do not expose inode to uio open/release hooks

On Wed, Dec 12, 2012 at 12:12:02AM +0100, Benedikt Spranger wrote:
> The inode parameter is unused by in kernel users of UIO.

Ok.

> Also the inode parameter makes it hard to resolve the existing open(),
> mmap() and close() difficulty.

I don't understand, what do you mean by this?  What is this parameter
causing problems with?

greg k-h
--
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/