All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>
Subject: Re: [Devel] [PATCH VZ10 v5 7/9] ve: Introduce per-VE failcount
Date: Mon, 17 Aug 2026 11:54:21 +0000	[thread overview]
Message-ID: <178696766161.213331.2446685212456143421.b4-review@b4> (raw)
In-Reply-To: <4ccd2bf8a399dd400c8cff87c01adb0c91294af7.1785669419.git.vladimir.riabchun@virtuozzo.com>

On Sun, 02 Aug 2026 11:40:37 +0000, Vladimir Riabchun <vladimir.riabchun@virtuozzo.com> wrote:
> diff --git a/kernel/ve/ve.c b/kernel/ve/ve.c
> index dc3faa0b1d76..a5c93be759ac 100644
> --- a/kernel/ve/ve.c
> +++ b/kernel/ve/ve.c
> @@ -1066,6 +1083,50 @@ VE_RESOURCE(mnt);
> [ ... skip 19 lines ... ]
> +static int ve_failcount_read(struct seq_file *sf, void *v)
> +{
> +	struct ve_struct *ve = css_to_ve(seq_css(sf));
> +	struct ve_failcount_entry *entry;
> +	atomic_t *fc;
> +

kernel/ve/ve.c: In function ?ve_failcount_read?:
kernel/ve/ve.c:1107:20: warning: assignment discards ?const? qualifier 
from pointer target type [-Wdiscarded-qualifiers]
 ?1107 |? ? ? ? ?for (entry = ve_failcounts; entry->name; entry++) {
 ? ? ? |? ? ? ? ? ? ? ? ? ? ^
kernel/ve/ve.c: In function ?ve_failcount_write?:
kernel/ve/ve.c:1121:20: warning: assignment discards ?const? qualifier 
from pointer target type [-Wdiscarded-qualifiers]
 ?1121 |? ? ? ? ?for (entry = ve_failcounts; entry->name; entry++) {

the left-hand pointee must carry all qualifiers of the right-hand pointee according to C11

-- 
Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>

  parent reply	other threads:[~2026-08-17 11:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02 11:40 [Devel] [PATCH VZ10 v5 0/9] Add per-VE failcount support Vladimir Riabchun
2026-08-02 11:40 ` [Devel] [PATCH VZ10 v5 1/9] ve/ve.{h, c}: Farewell to spaces as indents Vladimir Riabchun
2026-08-02 11:40 ` [Devel] [PATCH VZ10 v5 2/9] ve/namespace: Fix UAF in alloc_mnt_ns Vladimir Riabchun
2026-08-02 11:40 ` [Devel] [PATCH VZ10 v5 3/9] ve/fs: Rework per-ve mount count Vladimir Riabchun
2026-08-02 11:40 ` [Devel] [PATCH VZ10 v5 4/9] selftests/ve: Update ve_ns_owner_test Vladimir Riabchun
2026-08-02 11:40 ` [Devel] [PATCH VZ10 v5 5/9] ve: Move from global VE mounts limit to per-VE limit Vladimir Riabchun
2026-08-02 11:40 ` [Devel] [PATCH VZ10 v5 6/9] ve/ve.c: Generate VE resource accessors using macros Vladimir Riabchun
2026-08-02 11:40 ` [Devel] [PATCH VZ10 v5 7/9] ve: Introduce per-VE failcount Vladimir Riabchun
2026-08-07  9:25   ` Vasileios Almpanis
2026-08-17 11:54   ` Vasileios Almpanis [this message]
2026-08-02 11:40 ` [Devel] [PATCH VZ10 v5 8/9] selftests/ve: Add more helpers Vladimir Riabchun
2026-08-02 11:40 ` [Devel] [PATCH VZ10 v5 9/9] selftests/ve: Add mount accounting selftest Vladimir Riabchun
2026-08-07 10:01   ` Vasileios Almpanis
2026-08-17 11:54   ` Vasileios Almpanis
2026-08-17 11:54 ` [Devel] [PATCH VZ10 v5 0/9] Add per-VE failcount support Vasileios Almpanis
2026-08-17 14:09   ` Vasileios Almpanis

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=178696766161.213331.2446685212456143421.b4-review@b4 \
    --to=vasileios.almpanis@virtuozzo.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 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.