On Fri 27-02-15 11:40:39, Suzuki K. Poulose wrote:
> From: "Suzuki K. Poulose"
>
> With FAN_ONDIR set, the user can end up getting events, which
> it hasn't marked. This was revealed with fanotify04 testcase
> failure on Linux-4.0-rc1, and is a regression from 3.19, revealed
> with commit
On Fri 27-02-15 11:40:39, Suzuki K. Poulose wrote:
From: Suzuki K. Poulose suzuki.poul...@arm.com
With FAN_ONDIR set, the user can end up getting events, which
it hasn't marked. This was revealed with fanotify04 testcase
failure on Linux-4.0-rc1, and is a regression from 3.19, revealed
with
Hi Suzuki,
On 27.02.2015 12:40, Suzuki K. Poulose wrote:
> From: "Suzuki K. Poulose"
>
> With FAN_ONDIR set, the user can end up getting events, which
> it hasn't marked. This was revealed with fanotify04 testcase
> failure on Linux-4.0-rc1, and is a regression from 3.19, revealed
> with commit
Hi Suzuki,
On 27.02.2015 12:40, Suzuki K. Poulose wrote:
From: Suzuki K. Poulose suzuki.poul...@arm.com
With FAN_ONDIR set, the user can end up getting events, which
it hasn't marked. This was revealed with fanotify04 testcase
failure on Linux-4.0-rc1, and is a regression from 3.19,
From: "Suzuki K. Poulose"
With FAN_ONDIR set, the user can end up getting events, which
it hasn't marked. This was revealed with fanotify04 testcase
failure on Linux-4.0-rc1, and is a regression from 3.19, revealed
with commit (66ba93c0d7fe6: fanotify: don't set FAN_ONDIR implicitly
on a marks
From: Suzuki K. Poulose suzuki.poul...@arm.com
With FAN_ONDIR set, the user can end up getting events, which
it hasn't marked. This was revealed with fanotify04 testcase
failure on Linux-4.0-rc1, and is a regression from 3.19, revealed
with commit (66ba93c0d7fe6: fanotify: don't set FAN_ONDIR
6 matches
Mail list logo