All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Wang\, Yalin" <Yalin.Wang@sonymobile.com>,
	"'akpm\@linux-foundation.org'" <akpm@linux-foundation.org>,
	"'jani.nikula\@intel.com'" <jani.nikula@intel.com>,
	"'hch\@infradead.org'" <hch@infradead.org>,
	"'hare\@suse.de'" <hare@suse.de>,
	"'keescook\@chromium.org'" <keescook@chromium.org>,
	"'linux-kernel\@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] export module parameters even the permission is zero
Date: Tue, 20 Jan 2015 17:02:39 +1030	[thread overview]
Message-ID: <87lhkyarnc.fsf@rustcorp.com.au> (raw)
In-Reply-To: <35FD53F367049845BC99AC72306C23D103EDAF89E1A3@CNBJMBX05.corpusers.net>

"Wang, Yalin" <Yalin.Wang@sonymobile.com> writes:
> This patch make sure to export module parameters even the permission
> is zero, this is useful for some platforms like Android,
> the init process can change the parameter mode/owner by
> chmod/chown during bootup
>
> Signed-off-by: Yalin Wang <yalin.wang@sonymobile.com>

Hi!

        Unfortunately, this won't work.  Various parts of the code
assume that 0 permissions means "cannot be changed or read", so this
change would introduce many bugs (eg. the parameter could be
__initdata).

Since these are owned by root at boot, changing mode and owner should
still work.  However, you can't make a read-only field writable and
expect it to work.

Hope that helps,
Rusty.



> ---
>  kernel/params.c | 6 ------
>  1 file changed, 6 deletions(-)
>
> diff --git a/kernel/params.c b/kernel/params.c
> index bd65d136..aa80c04 100644
> --- a/kernel/params.c
> +++ b/kernel/params.c
> @@ -607,9 +607,6 @@ static __modinit int add_sysfs_param(struct module_kobject *mk,
>  	struct attribute **new_attrs;
>  	unsigned int i;
>  
> -	/* We don't bother calling this with invisible parameters. */
> -	BUG_ON(!kp->perm);
> -
>  	if (!mk->mp) {
>  		/* First allocation. */
>  		mk->mp = kzalloc(sizeof(*mk->mp), GFP_KERNEL);
> @@ -812,9 +809,6 @@ static void __init param_sysfs_builtin(void)
>  	for (kp = __start___param; kp < __stop___param; kp++) {
>  		char *dot;
>  
> -		if (kp->perm == 0)
> -			continue;
> -
>  		dot = strchr(kp->name, '.');
>  		if (!dot) {
>  			/* This happens for core_param() */
> -- 
> 2.1.3
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  parent reply	other threads:[~2015-01-20  6:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14  2:16 [RFC] export module parameters even the permission is zero Wang, Yalin
2015-01-14  5:46 ` Kees Cook
2015-01-20  6:32 ` Rusty Russell [this message]
2015-01-22  2:07   ` Wang, Yalin

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=87lhkyarnc.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=Yalin.Wang@sonymobile.com \
    --cc=akpm@linux-foundation.org \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=jani.nikula@intel.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.