public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jinseok Kim <always.starving0@gmail.com>
To: jack@suse.cz
Cc: amir73il@gmail.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	repnop@google.com, shuah@kernel.org
Subject: [RFC PATCH] selftests: fanotify: Add basic create/modify/delete event
Date: Thu,  5 Feb 2026 19:04:34 +0900	[thread overview]
Message-ID: <20260205100437.1834-1-always.starving0@gmail.com> (raw)
In-Reply-To: <dnncglg3x26gdsshcniw5yb4l2zlxz6qcwjqyekkpngb6v26q4@ftqnoe5eeapy>

Thanks for the feedback!

I agree LTP has very comprehensive fanotify/inotify tests.

However, the motivation for adding basic tests to kernel selftests is:
    - Quick and lightweight regression checking during kernel
    development/boot (no external LTP install needed)
    - Non-root basic cases (many LTP tests require root or complex setup)

Similar to how selftests/mm or selftests/net have basic syscall wrappers
even though LTP covers them deeply.

Do you think a different approach (LTP improvement instead)
would be better?

Thanks,
Jinseok

  reply	other threads:[~2026-02-05 10:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03 18:15 [RFC PATCH] selftests: fanotify: Add basic create/modify/delete event test Jinseok Kim
2026-02-04 12:56 ` Jan Kara
2026-02-05 10:04   ` Jinseok Kim [this message]
2026-02-05 11:34     ` [RFC PATCH] selftests: fanotify: Add basic create/modify/delete event Amir Goldstein
2026-02-05 12:55       ` Jinseok Kim
2026-02-05 12:21     ` Jan Kara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260205100437.1834-1-always.starving0@gmail.com \
    --to=always.starving0@gmail.com \
    --cc=amir73il@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=repnop@google.com \
    --cc=shuah@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox