[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210720160127.ac5e76d1e03a374b46f25077@linux-foundation.org>
Date: Tue, 20 Jul 2021 16:01:27 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Xiyu Yang <xiyuyang19@...an.edu.cn>
Cc: Alistair Popple <apopple@...dia.com>,
Yang Shi <shy828301@...il.com>,
Shakeel Butt <shakeelb@...gle.com>,
Hugh Dickins <hughd@...gle.com>,
Miaohe Lin <linmiaohe@...wei.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
yuanxzhang@...an.edu.cn, Xin Tan <tanxin.ctf@...il.com>,
Will Deacon <will.deacon@....com>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] mm/rmap: Convert from atomic_t to refcount_t on
anon_vma->refcount
On Mon, 19 Jul 2021 11:23:35 +0800 Xiyu Yang <xiyuyang19@...an.edu.cn> wrote:
> refcount_t type and corresponding API can protect refcounters from
> accidental underflow and overflow and further use-after-free situations.
Grumble.
For x86_64 defconfig this takes rmap.o text size from 13226 bytes to
13622.
For x86_64 allmodconfig this takes rmap.o text size from 66576 bytes to
67858.
I didn't check which config option is making the bloat so much worse,
but this really is quite bad. We bust a gut to make savings which are
1% the size of this! Is the refcount_t really so much better than a
bare atomic_t that this impact is justified?
Can someone pleeeeeeze take a look at what is happening here and put
the refcount code on a very serious diet?
Powered by blists - more mailing lists