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] [day] [month] [year] [list]
Message-ID: <201012211010.24701.tvrtko.ursulin@sophos.com>
Date:	Tue, 21 Dec 2010 10:10:24 +0000
From:	Tvrtko Ursulin <tvrtko.ursulin@...hos.com>
To:	Eric Paris <eparis@...hat.com>
CC:	"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"LinoSanfilippo@....de" <LinoSanfilippo@....de>,
	"alexey.zaytsev@...il.com" <alexey.zaytsev@...il.com>,
	"agruen@...bit.com" <agruen@...bit.com>
Subject: Re: [GIT PULL] notification bug fixes


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

Powered by Openwall GNU/*/Linux Powered by OpenVZ