[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230406120716.80980-1-frank.li@vivo.com>
Date: Thu, 6 Apr 2023 20:07:16 +0800
From: Yangtao Li <frank.li@...o.com>
To: gregkh@...uxfoundation.org
Cc: chao@...nel.org, damien.lemoal@...nsource.wdc.com,
frank.li@...o.com, huyue2@...lpad.com, jefflexu@...ux.alibaba.com,
jth@...nel.org, linux-erofs@...ts.ozlabs.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
naohiro.aota@....com, rafael@...nel.org, xiang@...nel.org
Subject: Re: [PATCH 2/3] erofs: convert to use kobject_is_added()
> Meta-comment, we need to come up with a "filesystem kobject type" to get
> rid of lots of the boilerplate filesystem kobject logic as it's
> duplicated in every filesystem in tiny different ways and lots of times
> (like here), it's wrong.
Can we add the following structure?
struct filesystem_kobject {
struct kobject kobject;
struct completion unregister;
};
w/ it, we can simplify something:
1. merge init_completion and kobject_init_and_add
2. merge kobject_put and wait_for_completion
3. we can have a common release func for kobj_type release
MBR,
Yangtao
Powered by blists - more mailing lists