[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150401085957.GF26339@quack.suse.cz>
Date: Wed, 1 Apr 2015 10:59:57 +0200
From: Jan Kara <jack@...e.cz>
To: Lino Sanfilippo <LinoSanfilippo@....de>
Cc: Fabian Frederick <fabf@...net.be>,
Andrew Morton <akpm@...ux-foundation.org>,
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 Sun 22-03-15 11:48:20, Lino Sanfilippo wrote:
> 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?
For now I'd stay calm. Events on directories with fanotify are hopelessly
useless anyway so I doubt anyone uses them. I just tested those in fanotify
LTP testcase for completeness (and screwed that up as you noted). If we
find a real application that tries to use directory events with fanotify
and which is broken by this patch, we'll have to revert it, that's for
sure.
Honza
--
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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/
Powered by blists - more mailing lists