linux-kernel - Re: [PATCH] bcb: Android bootloader control block driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120707230555.GA29514@kroah.com>
Date:	Sat, 7 Jul 2012 16:05:55 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Colin Cross <ccross@...roid.com>
Cc:	NeilBrown <neilb@...e.de>, Andrew Boie <andrew.p.boie@...el.com>,
	arve@...roid.com, rebecca@...roid.com, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] bcb: Android bootloader control block driver

On Sat, Jul 07, 2012 at 03:39:09PM -0700, Colin Cross wrote:
> On many (most?) ARM SoCs, the reboot flag is not stored on disk, or
> anywhere else userspace can access.  It is stored in a power
> management controller scratch register that survives resets, or a
> register in an external I2C PMIC, or in internal SoC RAM (I've seen
> all of these).  For your proposal, every SoC would need a custom API
> to save the reboot flag somewhere.  For these devices, it clearly
> makes more sense to use something like the REBOOT2 API, and if we have
> to use it on some devices, it makes no sense to me to not use it on
> other devices just because userspace could theoretically handle it.

That's fine, but that is not what this patch did at all.

Propose a patch that handles writing to those types of registers and we
will be glad to review it.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/