From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] tcindex01: Pass if the tcindex module is blacklisted
Date: Wed, 15 May 2024 15:46:05 +0200 [thread overview]
Message-ID: <20240515134605.GA227140@pevik> (raw)
In-Reply-To: <97937ba2-02b0-4682-baf9-0d97f678cb99@suse.cz>
> On 15. 05. 24 15:03, Petr Vorel wrote:
> > > > > +
> > > > > + if (!ret && TST_ERR == ENOENT) {
> > > > > + tst_res(TPASS | TTERRNO,
> > > > > + "tcindex module is blacklisted or unavailable");
> > Why not TCONF? We are testing if removing tcindex does not cause bug,
> > right?
> Blacklisting the module is intended as a partial CVE fix so TPASS is more
> appropriate than TCONF.
Thanks for info. Indeed it makes sense. Maybe it's just me, who didn't see it as
obvious when looking into CVE-2023-1829 description. But OK "We recommend
upgrading past commit 8c710f75256bb3cf05ac7b1672c82b92c43f3d28." + your
description makes it clear that some distros just preferred blacklist
configuration instead of backporting the removal commit.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2024-05-15 13:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 9:47 [LTP] [PATCH] tcindex01: Pass if the tcindex module is blacklisted Martin Doucha
2024-05-15 10:15 ` Petr Vorel
2024-05-15 10:53 ` Cyril Hrubis
2024-05-15 12:22 ` Petr Vorel
2024-05-15 12:34 ` Martin Doucha
2024-05-15 13:09 ` Petr Vorel
2024-05-15 13:03 ` Petr Vorel
2024-05-15 13:38 ` Martin Doucha
2024-05-15 13:46 ` Petr Vorel [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=20240515134605.GA227140@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@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 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.