From: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>
To: Eric Paris <eparis@redhat.com>
Cc: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"LinoSanfilippo@gmx.de" <LinoSanfilippo@gmx.de>,
"alexey.zaytsev@gmail.com" <alexey.zaytsev@gmail.com>,
"agruen@linbit.com" <agruen@linbit.com>
Subject: Re: [GIT PULL] notification bug fixes
Date: Tue, 21 Dec 2010 10:10:24 +0000 [thread overview]
Message-ID: <201012211010.24701.tvrtko.ursulin@sophos.com> (raw)
In-Reply-To: <1292440647.3042.8.camel@localhost.localdomain>
Hi,
On Wednesday 15 Dec 2010 19:17:27 Eric Paris wrote:
> The notable fixes in this pull request include a potential deadlock when
> fanotify listeners exit, an unpriv user kernel memory DoS in inotify,
> and an API (although not ABI) change in fanotify's userspace message to
> support expansion in the next release.
Would you consider pushing e3366737eeee6c3c482af3758c6dcb65eccfa62d and
dependencies (ba611b1c12a230785c25a7b3a5ea948fda8cc137,
http://marc.info/?l=linux-kernel&m=129200322526558&w=2)? It would make it
easier for userspace if first published kernel already had
FAN_READONLY_FALLBACK.
Which also reminds me, would a way to explicitly get the protocol version be
useful?
Tvrtko
Sophos Limited, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom.
Company Reg No 2096520. VAT Reg No GB 991 2418 08.
prev parent reply other threads:[~2010-12-21 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 19:17 Eric Paris
2010-12-21 10:10 ` Tvrtko Ursulin [this message]
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=201012211010.24701.tvrtko.ursulin@sophos.com \
--to=tvrtko.ursulin@sophos.com \
--cc=LinoSanfilippo@gmx.de \
--cc=agruen@linbit.com \
--cc=alexey.zaytsev@gmail.com \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®