[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87d046sj8w.fsf@x220.int.ebiederm.org>
Date: Tue, 04 Aug 2020 07:11:59 -0500
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Christian Brauner <christian.brauner@...ntu.com>
Cc: Kirill Tkhai <ktkhai@...tuozzo.com>, akpm@...ux-foundation.org,
viro@...iv.linux.org.uk, adobriyan@...il.com, davem@...emloft.net,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/8] namespaces: Introduce generic refcount
Christian Brauner <christian.brauner@...ntu.com> writes:
> On Mon, Aug 03, 2020 at 01:16:10PM +0300, Kirill Tkhai wrote:
>> Every namespace type has its own counter. Some of them are
>> of refcount_t, some of them are of kref.
>>
>> This patchset introduces generic ns_common::count for any
>> type of namespaces instead of them.
>>
>> ---
>
> I was wondering why that series never made it to me turns out there's
> some weird bug in my (neo)mutt where it sometimes marks messages as read
> when I'm deleting completely unrelated messages. That has already cost
> me a talk slot for an event I really wanted to attend and now it seems
> to start costing me patches... I need to figure this out.
>
> Anyway, thanks for sending this. I pulled this into my tree now.
Actually why in the world should the reference count be generic?
What is the point of this patchset?
What problem does it solve. Name spaces are not the same, and
their refcounting needs are not the same so I don't have a clue how it
helps anything to have a reference count in ns_common.
Eric
Powered by blists - more mailing lists