From: Lino Sanfilippo <LinoSanfilippo@gmx.de>
To: Fabian Frederick <fabf@skynet.be>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Eric Paris <eparis@redhat.com>,
linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>,
Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 1/1 linux-next] fanotify: fix a lock in fanotify_should_send_event()
Date: Sun, 22 Mar 2015 11:48:20 +0100 [thread overview]
Message-ID: <550E9DF4.7@gmx.de> (raw)
In-Reply-To: <1702390928.185057.1427017594441.open-xchange@webmail.nmp.proximus.be>
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
next prev parent reply other threads:[~2015-03-22 10:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 20:56 [PATCH 1/1 linux-next] fanotify: fix a lock in fanotify_should_send_event() Fabian Frederick
2015-03-20 21:09 ` Andrew Morton
2015-03-20 21:16 ` Fabian Frederick
2015-03-21 1:01 ` Lino Sanfilippo
2015-03-21 1:15 ` Lino Sanfilippo
2015-03-22 9:46 ` Fabian Frederick
2015-03-22 10:48 ` Lino Sanfilippo [this message]
2015-04-01 8:59 ` Jan Kara
2015-03-21 0:56 ` Lino Sanfilippo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=550E9DF4.7@gmx.de \
--to=linosanfilippo@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=eparis@redhat.com \
--cc=fabf@skynet.be \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox