From: "Theodore Tso" <tytso@mit.edu>
To: Artem Dinaburg <artem@trailofbits.com>
Cc: stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>,
Max Kellermann <max.kellermann@ionos.com>,
Zhang Yi <yi.zhang@huawei.com>, Jan Kara <jack@suse.cz>,
Jan Kara <jack@suse.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.6.y 0/2] jbd2: backport CVE-2026-89566, CVE-2026-89567
Date: Sat, 10 Oct 2026 19:53:14 -0400 [thread overview]
Message-ID: <asrNX2qBf5qBrFLu@mit.edu> (raw)
In-Reply-To: <CAP3zxaC92rwQNCpuK_tXR9THQOecVoZwxg8ZUgYt=0iKiMsuxg@mail.gmail.com>
On Sat, Oct 10, 2026 at 06:12:10PM -0500, Artem Dinaburg wrote:
>
> Our initial unpatched/patched runs showed some differences in both
> directions. We cannot yet attribute those to the series, so we have
> paused the patched comparison and are running three complete
> iterations on the same unpatched baseline to assess repeatability.
Note that some tests can be flaky. So when you see a test failure, it
can be useful to run a test multiple times, so you can see if the test
is a reliable hard failure, or one that only fails, say, 30% of the
time. So to run generic/363 10 times in the ext4/1k configuration,
you might do soemthing like this:
kvm-xfstests -c ext4/1k generic/363 -C 10
- Ted
prev parent reply other threads:[~2026-10-10 23:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 19:20 Artem Dinaburg
2026-10-08 19:20 ` [PATCH 6.6.y 1/2] jbd2: check need_resched() when skipping busy checkpoint buffers Artem Dinaburg
2026-10-08 19:20 ` [PATCH 6.6.y 2/2] jbd2: bound shrinker scans by examined " Artem Dinaburg
2026-10-09 17:09 ` [PATCH 6.6.y 0/2] jbd2: backport CVE-2026-89566, CVE-2026-89567 Sasha Levin
2026-10-09 18:29 ` Theodore Tso
2026-10-10 22:12 ` Artem Dinaburg
2026-10-10 23:53 ` Theodore Tso [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=asrNX2qBf5qBrFLu@mit.edu \
--to=tytso@mit.edu \
--cc=artem@trailofbits.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max.kellermann@ionos.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yi.zhang@huawei.com \
/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
all inboxes | Powered by JetHome®