[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c9c572ed-05a1-cec9-97e9-2b66cb58afcc@intel.com>
Date: Mon, 19 Nov 2018 09:06:15 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Yangtao Li <tiny.windzz@...il.com>, keescook@...omium.org,
dave.hansen@...ux.intel.com, luto@...nel.org, peterz@...radead.org,
tglx@...utronix.de, mingo@...hat.com, bp@...en8.de, hpa@...or.com
Cc: x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/mm/dump_pagetables: Change to use
DEFINE_SHOW_ATTRIBUTE macro
On 11/19/18 7:43 AM, Yangtao Li wrote:
> -static const struct file_operations ptdump_curusr_fops = {
> - .owner = THIS_MODULE,
> - .open = ptdump_open_curusr,
> - .read = seq_read,
> - .llseek = seq_lseek,
> - .release = single_release,
> -};
> +DEFINE_SHOW_ATTRIBUTE(ptdump_curusr);
FWIW, I rather dislike this conversion and the DEFINE_SHOW_ATTRIBUTE()
approach in general. It makes it basically impossible to go from
ptdump_curusr to ptdump_open_curusr without opening up the macro and
reverse-engineering it.
My test is that for these macros to be sane, I need to be able to find
"ptdump_open_curusr" by grepping for "ptdump_curusr". This fails the test.
I don't think saving a few lines of code is worth the obfuscation.
Powered by blists - more mailing lists