All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Sasha Levin <sashal@kernel.org>, Jan Kara <jack@suse.cz>,
	Matthew Bobrowski <repnop@google.com>,
	"stable-commits@vger.kernel.org" <stable-commits@vger.kernel.org>,
	ltp@lists.linux.it
Subject: Re: [LTP] Patch "fsnotify: consistent behavior for parent not watching children" has been added to the 5.15-stable tree
Date: Fri, 30 Aug 2024 22:35:01 +0200	[thread overview]
Message-ID: <20240830203501.GA94648@pevik> (raw)
In-Reply-To: <ACB7BCB8-E6EA-41DC-8228-881081AA0596@oracle.com>

Hi Chuck,

> Hi Amir-

> > On Mar 20, 2024, at 2:57 AM, Amir Goldstein <amir73il@gmail.com> wrote:

> > Please follow up in adjusting the LTP test fanotify09 to update this
> > comment with the appropriate 5.15.y version:

> > * Test cases #6-#7 are regression tests for commit:
> > * (from v5.19, unlikely to be backported thus not in .tags):
> > *
> > *      e730558adffb fanotify: consistent behavior for parent not
> > watching children

> > As well as this hackish test condition:

> >        if (tc->ignore && tst_kvercmp(5, 19, 0) < 0) {
> >                tst_res(TCONF, "ignored mask on parent dir has undefined "
> >                                "behavior on kernel < 5.19");
> >                return;
> >        }

> I'm not sure how this check should be altered.

> The fix in question now appears in both 5.10.220 and
> 5.15.154. Which means the commit is in, for instance,
> 5.10.222 and 5.15.160, but not in 5.13.0 or 5.17.0.

Thank you for noticing that. The comment on the test patch [1] was:

 * Test cases #6-#7 are regression tests for commit:
 * (from v5.19, unlikely to be backported thus not in .tags):

I see in the end it got backported. Now we have to decide whether it's important
enough that we should put commit in the tag and run it unconditionally
(preferred way for fixes) or from the latest stable kernel version which got the
backport.

AFAIK LTP should not try to hide bugs, report missing fix. And it's up to
testers and the projects if they consider the problem as WONTFIX or the kernel
they test will backport the fix.

Kind regards,
Petr

[1] https://lore.kernel.org/ltp/20220620132737.2015073-5-amir73il@gmail.com/

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

       reply	other threads:[~2024-08-30 20:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240318231603.2221376-1-sashal@kernel.org>
     [not found] ` <CAOQ4uxjxSQESOZVCV_yL=uwG5+Y89sYRozVSgHPpaudG4CwZqw@mail.gmail.com>
     [not found]   ` <ACB7BCB8-E6EA-41DC-8228-881081AA0596@oracle.com>
2024-08-30 20:35     ` Petr Vorel [this message]
2024-08-30 20:58       ` [LTP] Patch "fsnotify: consistent behavior for parent not watching children" has been added to the 5.15-stable tree Amir Goldstein

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=20240830203501.GA94648@pevik \
    --to=pvorel@suse.cz \
    --cc=chuck.lever@oracle.com \
    --cc=jack@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=repnop@google.com \
    --cc=sashal@kernel.org \
    --cc=stable-commits@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.