linux-kernel - Re: [PATCH] fuse: don't check for file->private

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: <54638DD6.60009@posteo.de>
Date:	Wed, 12 Nov 2014 17:41:58 +0100
From:	Martin Kepplinger <martink@...teo.de>
To:	miklos@...redi.hu
CC:	fuse-devel@...ts.sourceforge.net, thierry.reding@...il.com,
	gregkh@...uxfoundation.org, giedriuswork@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fuse: don't check for file->private_data on open().

Am 2014-11-12 um 17:31 schrieb Martin Kepplinger:
> The miscdevice core now sets file->private_data to the struct miscdevice
> so don't fail when this is not NULL.
> 
> Reported-by: Thierry Reding <thierry.reding@...il.com>
> Signed-off-by: Martin Kepplinger <martink@...teo.de>
> ---
> This is a question: what does this check provide and does overwriting
> file->private_data make any difference?
> 
> Is open() by the user not allowed here, if file->private_data is set?
> 
> thanks!!
> 

if ok, please add

Reported-by: Giedrius Statkevicius <giedriuswork@...il.com>

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