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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 18 Nov 2021 18:57:35 -0500 From: Gabriel Krisman Bertazi <krisman@...labora.com> To: pvorel@...e.cz, jack@...e.com, amir73il@...il.com, repnop@...gle.com Cc: linux-ext4@...r.kernel.org, kernel@...labora.com, khazhy@...gle.com, ltp@...ts.linux.it, Gabriel Krisman Bertazi <krisman@...labora.com> Subject: [PATCH v4 0/9] Test the new fanotify FAN_FS_ERROR event Hi, FAN_FS_ERROR was merged into Linus tree, and the PIDFD testcases reached LTP. Therefore, I'm sending a new version of the FAN_FS_ERROR LTP tests. This is the v4 of this patchset, and it applies the feedback of the previous version. Thanks, --- Original cover letter: FAN_FS_ERROR is a new (still unmerged) fanotify event to monitor fileystem errors. This patchset introduces a new LTP test for this feature. Testing file system errors is slightly tricky, in particular because they are mostly file system dependent. Since there are only patches for ext4, I choose to make the test around it, since there wouldn't be much to do with other file systems. The second challenge is how we cause the file system errors, since there is no error injection for ext4 in Linux. In this series, this is done by corrupting specific data in the test device with the help of debugfs. The FAN_FS_ERROR feature is flying around linux-ext4 and fsdevel, and the latest version is available on the branch below: https://gitlab.collabora.com/krisman/linux -b fanotify-notifications-v9 A proper manpage description is also available on the respective mailing list, or in the branch below: https://gitlab.collabora.com/krisman/man-pages.git -b fan-fs-error Please, let me know your thoughts. Gabriel Krisman Bertazi (9): syscalls: fanotify: Add macro to require specific mark types syscalls: fanotify: Add macro to require specific events syscalls/fanotify22: Introduce FAN_FS_ERROR test syscalls/fanotify22: Validate the generic error info syscalls/fanotify22: Validate incoming FID in FAN_FS_ERROR syscalls/fanotify22: Support submission of debugfs commands syscalls/fanotify22: Create a corrupted file syscalls/fanotify22: Test file event with broken inode syscalls/fanotify22: Test capture of multiple errors configure.ac | 3 +- testcases/kernel/syscalls/fanotify/.gitignore | 1 + testcases/kernel/syscalls/fanotify/fanotify.h | 65 +++- .../kernel/syscalls/fanotify/fanotify03.c | 4 +- .../kernel/syscalls/fanotify/fanotify10.c | 3 +- .../kernel/syscalls/fanotify/fanotify12.c | 3 +- .../kernel/syscalls/fanotify/fanotify22.c | 314 ++++++++++++++++++ 7 files changed, 385 insertions(+), 8 deletions(-) create mode 100644 testcases/kernel/syscalls/fanotify/fanotify22.c -- 2.33.0
Powered by blists - more mailing lists