From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Brian Norris <computersforpeace@gmail.com>
Subject: Re: [PATCH v2 2/2] UBI: Make mtd parameter readable
Date: Tue, 10 Jan 2017 15:48:31 +0200 [thread overview]
Message-ID: <1484056111.2133.16.camel@linux.intel.com> (raw)
In-Reply-To: <CAFLxGvyTKH-7X0byYOYardGZXGQZtpHTr=aRhqD6WunDqXbneg@mail.gmail.com>
On Tue, 2017-01-10 at 14:33 +0100, Richard Weinberger wrote:
> Andy,
>
> On Tue, Jan 10, 2017 at 1:56 PM, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > Fix permissions to allow read mtd parameter back (only for owner).
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> Please CC all maintainers in future. Otherwise the chance is high that
> I'll miss a patch.
Noted.
> > -module_param_call(mtd, ubi_mtd_param_parse, NULL, NULL, 000);
> > +module_param_call(mtd, ubi_mtd_param_parse, NULL, NULL, 0400);
> What is the use case?
> AFAIKT the permissions are 000
If it's not 0 in current case than you easily crash the kernel because
parser will be gone at that time. This is fixed by patch 1.
> because a parser is involved and to
> "understand" the parameter,
> a reader needs the ubi_mtd_param_parse() function.
Are you implying that writer is a bot and reader is human being?
The use case is obvious (any security reasons are implied?) -- allow
user to see what was written there in the first place.
Permissions 0000 are error prone.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-01-10 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 12:56 [PATCH v2 1/2] UBI: Fix section mismatch Andy Shevchenko
2017-01-10 12:56 ` [PATCH v2 2/2] UBI: Make mtd parameter readable Andy Shevchenko
2017-01-10 13:33 ` Richard Weinberger
2017-01-10 13:48 ` Andy Shevchenko [this message]
2017-01-10 13:54 ` Richard Weinberger
2017-01-10 14:11 ` Andy Shevchenko
2017-01-10 14:16 ` Richard Weinberger
2017-01-10 14:35 ` Andy Shevchenko
2017-01-10 15:31 ` Richard Weinberger
2017-01-10 15:38 ` Andy Shevchenko
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=1484056111.2133.16.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
/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.