All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andrei Warkentin <awarkentin@vmware.com>,
	Ulf Hansson <ulf.hansson@stericsson.com>,
	Per Forlin <per.forlin@stericsson.com>,
	Lee Jones <lee.jones@linaro.org>,
	Johan Rudholm <johan.rudholm@stericsson.com>,
	John Beckett <john.beckett@stericsson.com>,
	linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: boot partition ro lock support
Date: Sat, 22 Oct 2011 12:55:01 -0400	[thread overview]
Message-ID: <m2vcrh55lm.fsf@bob.laptop.org> (raw)
In-Reply-To: <CACRpkdY5T+QoyLvsPmwQRcNPoV=U=46LRGzKvK_8fSL8kurSwA@mail.gmail.com> (Linus Walleij's message of "Sat, 22 Oct 2011 18:33:57 +0200")

Hi Linus,

On Sat, Oct 22 2011, Linus Walleij wrote:
> So what about a cmdline approach? That makes it possible
> for people who are willingly recompiling and hacking their kernels
> to tinker with this if they absolutely want to go in on that
> partition, make it rw and change stuff.
>
> ...org have I just got all this backwards...?

Regarding this patch, we're not so worried that someone will take a
read-only boot partition and make it read-write and do something wrong;
sysfs is good enough to protect against that happening (at least by
mistake).

What we're worried about is someone issuing the perm read-only command,
and not realizing that it really means that they can never ever write
any more changes to their eMMC -- it's a one-time fuse -- and perhaps
further not realizing that this may make their expensive cell phone
become a brick of some sort, depending on how much the bootloader or
OS depends on having r/w access.

I don't even know that I'd want to make such an option available via a
boot argument, since boot arguments are often misunderstood.  As Andrei
says, it doesn't sound like something a regular user (as opposed to an
OEM) should ever have reason to do.  I'd rather leave it to specialized
manufacturing equipment.

Does that make sense?  Thanks,

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2011-10-22 16:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-21 13:17 [PATCH] mmc: boot partition ro lock support Ulf Hansson
2011-10-22  1:44 ` Andrei Warkentin
2011-10-22 10:32   ` Chris Ball
2011-10-22 16:33     ` Linus Walleij
2011-10-22 16:55       ` Chris Ball [this message]
2011-10-23  0:51         ` Sebastian Rasmussen
2011-10-23  6:38           ` Chris Ball
2011-10-24  9:23             ` Ulf Hansson
2011-10-24 10:08               ` Chris Ball
2011-10-24 12:22                 ` Johan RUDHOLM
2011-10-25 21:31                   ` Andrei E. Warkentin
2011-11-22 12:15                 ` Johan RUDHOLM
2011-10-24 18:20             ` J Freyensee

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=m2vcrh55lm.fsf@bob.laptop.org \
    --to=cjb@laptop.org \
    --cc=awarkentin@vmware.com \
    --cc=johan.rudholm@stericsson.com \
    --cc=john.beckett@stericsson.com \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=per.forlin@stericsson.com \
    --cc=ulf.hansson@stericsson.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.