From: Al Viro <viro@zeniv.linux.org.uk>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Eric Biggers <ebiggers@google.com>,
linux-fsdevel@vger.kernel.org, LTP List <ltp@lists.linux.it>,
Petr Vorel <pvorel@suse.cz>
Subject: Re: interesting breakage in ltp fanotify10
Date: Mon, 23 Jun 2025 16:38:00 +0100 [thread overview]
Message-ID: <20250623153800.GE1880847@ZenIV> (raw)
In-Reply-To: <CAOQ4uxhTXgTt62cX-F00e4vAyhDn=fCTxDqONcGT9+tBH-DkCQ@mail.gmail.com>
On Mon, Jun 23, 2025 at 05:19:26PM +0200, Amir Goldstein wrote:
> I have no idea where this strange TWARN is coming from
> I did not investigate it, but the bug is there anyway, so I sent a fix.
OK... Current LTP + patch you've posted does not screw that sysctl
anymore, so... Tested-by: Al Viro <viro@zeniv.linux.org.uk>
prev parent reply other threads:[~2025-06-23 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 21:51 interesting breakage in ltp fanotify10 Al Viro
2025-06-23 7:24 ` Amir Goldstein
2025-06-23 14:45 ` Al Viro
2025-06-23 15:19 ` Amir Goldstein
2025-06-23 15:38 ` Al Viro [this message]
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=20250623153800.GE1880847@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=amir73il@gmail.com \
--cc=ebiggers@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).