netdev - Re: [PATCH 0/2] mark some slabs as visible not mergeable

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] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 26 Feb 2018 15:15:02 -0500 (EST)
From:   David Miller <davem@...hat.com>
To:     stephen@...workplumber.org
Cc:     willy@...radead.org, netdev@...r.kernel.org, linux-mm@...ck.org,
        ikomyagin@...il.com, sthemmin@...rosoft.com
Subject: Re: [PATCH 0/2] mark some slabs as visible not mergeable

From: Stephen Hemminger <stephen@...workplumber.org>
Date: Sat, 24 Feb 2018 11:04:52 -0800

> This fixes an old bug in iproute2's ss command because it was
> reading slabinfo to get statistics. There isn't a better API
> to do this, and one can argue that /proc is a UAPI that must
> not change.

Please elaborate what kind of statistics are needed.

> Therefore this patch set adds a flag to slab to give another
> reason to prevent merging, and then uses it in network code.
> 
> The patches are against davem's linux-net tree and should also
> goto stable as well.

Well, as has been pointed out this never worked with SLUB so
in some sense this was always broken.

And the "UAPI" of slabinfo is to show the state of the various
slab caches.  And that's it.

If the implementation does merging or whatever, the UAPI is expressing
that and it's perfectly legitimate and not breaking UAPI in my
opinion.

I think the better solution is to grab the information from somewhere
else, so let's move this conversation along with the answer to my
question about asking for more details about what is needed by
iproute2.

Thank you.