linux-kernel - Re: [PATCH 1/1 linux-next] fanotify: fix a lock in fanotify_should_send

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 22 Mar 2015 11:48:20 +0100
From:	Lino Sanfilippo <LinoSanfilippo@....de>
To:	Fabian Frederick <fabf@...net.be>,
	Andrew Morton <akpm@...ux-foundation.org>
CC:	Eric Paris <eparis@...hat.com>, linux-kernel@...r.kernel.org,
	David Howells <dhowells@...hat.com>, Jan Kara <jack@...e.cz>
Subject: Re: [PATCH 1/1 linux-next] fanotify: fix a lock in fanotify_should_send_event()

On 22.03.2015 10:46, Fabian Frederick wrote:

> Let's hope it only breaks ltp tests and no _real_ userland stuff
> (search systems ...)
> 
> Regards,
> Fabian
> 

Hi Fabian,

yes, that worries me too. I know that there have been discussions on
lkml in which it was made clear that userspace breakage is frowned upon.
And it is obvious, that the latest changes concerning the handling of
FAN_ONDIR are also visible to userspace. But since the concerning
patches have been accepted I think it is ok. I could be wrong though.

Maybe someone with a deeper knowledge of kernel policy/guidelines could
comment on this?

Regards,
Lino

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