From: Song Liu <songliubraving@meta.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Song Liu <song@kernel.org>,
"linux-modules@vger.kernel.org" <linux-modules@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
Kernel Team <kernel-team@meta.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Guenter Roeck <linux@roeck-us.net>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Subject: Re: [PATCH v7] module: replace module_layout with module_memory
Date: Wed, 1 Feb 2023 22:28:01 +0000 [thread overview]
Message-ID: <BBCAAD9D-245A-4068-B7C7-01DA4E02261C@fb.com> (raw)
In-Reply-To: <Y9rYcvPx4MhA+c+u@hirez.programming.kicks-ass.net>
> On Feb 1, 2023, at 1:24 PM, Peter Zijlstra <peterz@infradead.org> wrote:
>
> On Wed, Feb 01, 2023 at 10:44:22AM -0800, Song Liu wrote:
>
>> static ssize_t show_datasize(struct module_attribute *mattr,
>> struct module_kobject *mk, char *buffer)
>> {
>> - return sprintf(buffer, "%u\n", mk->mod->data_layout.size);
>> + unsigned int size = 0;
>> +
>> + for_class_mod_mem_type(type, core) {
>> + if (type == MOD_TEXT)
>> + continue;
>
> isn't this the same as:
>
> for_class_mod_mem_type(type, core_data)
>
> ?
Great catch!
>
>> + size += mk->mod->mem[type].size;
>> + }
>> + return sprintf(buffer, "%u\n", size);
>> }
>
>
>> - lockdep_free_key_range(mod->data_layout.base, mod->data_layout.size);
>> + for_class_mod_mem_type(type, core) {
>> + lockdep_free_key_range(mod->mem[type].base,
>> + mod->mem[type].size);
>> + }
>
> Why the core_data to core change? Specifically the difference seems to
> be you now include text. Now, we shouldn't be having lockdep keys in
> text, so it's harmless, still a bit weird.
Will fix!
Thanks,
Song
prev parent reply other threads:[~2023-02-01 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 18:44 Song Liu
2023-02-01 21:24 ` Peter Zijlstra
2023-02-01 22:28 ` Song Liu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BBCAAD9D-245A-4068-B7C7-01DA4E02261C@fb.com \
--to=songliubraving@meta.com \
--cc=christophe.leroy@csgroup.eu \
--cc=hch@lst.de \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mcgrof@kernel.org \
--cc=peterz@infradead.org \
--cc=song@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®