linux-kernel - Re: [PATCH 1/1] alloc_tag: mark inaccurate allocation counters in /proc/allocinfo output

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAJuCfpF7NaUJk7fwPQ7-V6DPaTo4eqL-5Xxs7iO0nzNDS9N7nQ@mail.gmail.com>
Date: Mon, 15 Sep 2025 16:04:06 -0700
From: Suren Baghdasaryan <surenb@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Usama Arif <usamaarif642@...il.com>, Yueyang Pan <pyyjason@...il.com>, 
	David Wang <00107082@....com>, kent.overstreet@...ux.dev, vbabka@...e.cz, 
	hannes@...xchg.org, rientjes@...gle.com, roman.gushchin@...ux.dev, 
	harry.yoo@...cle.com, shakeel.butt@...ux.dev, pasha.tatashin@...een.com, 
	souravpanda@...gle.com, linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] alloc_tag: mark inaccurate allocation counters in
 /proc/allocinfo output

On Thu, Sep 11, 2025 at 2:31 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Thu, 11 Sep 2025 12:00:23 -0400 Usama Arif <usamaarif642@...il.com> wrote:
>
> > > I think simply adding * to the end of function name or filename is sufficient
> > > as they are already str.
> > >
> >
> > Instead of:
> >
> > 49152*      48* arch/x86/kernel/cpu/mce/core.c:2709 func:mce_device_create
> >
> > Could we do something like:
> >
> > 49152      48 arch/x86/kernel/cpu/mce/core.c:2709 func:mce_device_create(inaccurate)
>
> Can we add another row, saying "the previous row was inaccurate"?  I
> guess that would break parsers also.
>
>
>
> I don't know if this was by design, but the present format does provide
> extensibility.  It is basically
>
>         NNNN NNN name:value name:value
>
> one could arguably append a third name:value and hope that authors of
> existing parsers figured this out.
>
>
> Whatev.  I'll drop this version from mm.git.

v2 is posted at:
https://lore.kernel.org/all/20250915230224.4115531-1-surenb@google.com/
Thanks!