[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1721718387-9038-1-git-send-email-ajay.kaher@broadcom.com>
Date: Tue, 23 Jul 2024 12:36:27 +0530
From: Ajay Kaher <ajay.kaher@...adcom.com>
To: gregkh@...uxfoundation.org
Cc: amir73il@...il.com,
chuck.lever@...cle.com,
jack@...e.cz,
krisman@...labora.com,
patches@...ts.linux.dev,
sashal@...nel.org,
stable@...r.kernel.org,
adilger.kernel@...ger.ca,
linux-ext4@...r.kernel.org,
tytso@....edu,
ajay.kaher@...adcom.com,
alexey.makhalov@...adcom.com,
vasavi.sirnapalli@...adcom.com,
florian.fainelli@...adcom.com
Subject: [PATCH 5.10 387/770] fanotify: Allow users to request FAN_FS_ERROR events
> [ Upstream commit 9709bd548f11a092d124698118013f66e1740f9b ]
>
> Wire up the FAN_FS_ERROR event in the fanotify_mark syscall, allowing
> user space to request the monitoring of FAN_FS_ERROR events.
>
> These events are limited to filesystem marks, so check it is the
> case in the syscall handler.
Greg,
Without 9709bd548f11 in v5.10.y skips LTP fanotify22 test case, as:
fanotify22.c:312: TCONF: FAN_FS_ERROR not supported in kernel
With 9709bd548f11 in v5.10.220, LTP fanotify22 is failing because of
timeout as no notification. To fix need to merge following two upstream
commit to v5.10:
124e7c61deb27d758df5ec0521c36cf08d417f7a:
0001-ext4_fix_error_code_saved_on_super_block_during_file_system.patch
https://lore.kernel.org/stable/1721717240-8786-1-git-send-email-ajay.kaher@broadcom.com/T/#mf76930487697d8c1383ed5d21678fe504e8e2305
9a089b21f79b47eed240d4da7ea0d049de7c9b4d:
0001-ext4_Send_notifications_on_error.patch
Link: https://lore.kernel.org/stable/1721717240-8786-1-git-send-email-ajay.kaher@broadcom.com/T/#md1be98e0ecafe4f92d7b61c048e15bcf286cbd53
-Ajay
Powered by blists - more mailing lists