linux-kernel - [PATCH 0/5 v2] Fanotify cleanups

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-next>] [day] [month] [year] [list]

Date:	Mon,  3 Mar 2014 12:12:18 +0100
From:	Jan Kara <jack@...e.cz>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	LKML <linux-kernel@...r.kernel.org>, linux-fsdevel@...r.kernel.org,
	Eric Paris <eparis@...isplace.org>, Jan Kara <jack@...e.cz>
Subject: [PATCH 0/5 v2] Fanotify cleanups

  Hello,

  when fixing use-after-free bug with fanotify introduced by my previous
cleanup patches (the fix is already merged by Linus), I have better understood
handling of permission events and found a couple of things that can be further
cleaned up.  This patch series uses the notify structure itself for processing
response to permission event (patch 2/5) thus saving some space and allocation,
converts access_mutex to spinlock (patch 3/5) which should be faster, and moves
code around copy_event_to_user() to make code more readable (patch 4/5, 5/5).

The patches pass LTP fanotify tests. Andrew, can you please take the patches?

Changes since v1:
- rebased on top of latest fanotify fixes which went to Linus (3.13-rc5)

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