public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v3 2/2] Add test for CVE 2021-38198
Date: Mon, 6 May 2024 22:02:10 +0200	[thread overview]
Message-ID: <20240506200210.GB38981@pevik> (raw)
In-Reply-To: <20240506191739.GA36275@pevik>

Hi Martin, Cyril,

> Hi Martin, Cyril,

> > +static struct tst_test test = {
> > +	.test_all = tst_kvm_run,
> > +	.setup = setup,
> > +	.cleanup = tst_kvm_cleanup,
> > +	.needs_root = 1,

> This test was merged some time ago.

> FYI this .needs_root generates -Wsingle-bit-bitfield-constant-conversion error.
> Nothing important, maybe you see an easy way to fix it.

> kvm_pagefault01.c:218:16: warning: implicit truncation from 'int' to a one-bit wide bit-field changes value from 1 to -1 [-Wsingle-bit-bitfield-constant-conversion]
>         .needs_root = 1,
>                       ^
> 1 warning generated.

I'm sorry, this is not specific to KVM tests (and indeed, I was not able to find
how this could be specific), but to any test built with clang (gcc simply does
not issue this error). Obviously the problem is for any 1 bit field member in
struct tst_test. The fix is quite simple - turn them to unsigned int.

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/commit/?id=eab9100d9898cbd37882b04415b12156f8942f18

Kind regards,
Petr

> Kind regards,
> Petr

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

      reply	other threads:[~2024-05-06 20:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21 12:33 [LTP] [PATCH v3 0/2] KVM testing Martin Doucha
2022-04-21 12:33 ` [LTP] [PATCH v3 1/2] KVM test infrastructure Martin Doucha
2022-04-21 13:07   ` Cyril Hrubis
2022-04-21 12:33 ` [LTP] [PATCH v3 2/2] Add test for CVE 2021-38198 Martin Doucha
2022-04-21 13:07   ` Cyril Hrubis
2024-05-06 19:17   ` Petr Vorel
2024-05-06 20:02     ` 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=20240506200210.GB38981@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox