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: <20180725182745.6e436abc@aktux>
Date:   Wed, 25 Jul 2018 18:27:45 +0200
From:   Andreas Kemnade <andreas@...nade.info>
To:     Ladislav Michl <ladis@...ux-mips.org>
Cc:     Discussions about the Letux Kernel <letux-kernel@...nphoenux.org>,
        "H. Nikolaus Schaller" <hns@...delico.com>,
        Mark Rutland <mark.rutland@....com>,
        devicetree@...r.kernel.org, Tony Lindgren <tony@...mide.com>,
        linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
        BenoƮt Cousson <bcousson@...libre.com>,
        linux-omap@...r.kernel.org
Subject: Re: [Letux-kernel] [PATCH 09/32] ARM: dts: omap3-gta04: make NAND
 partitions compatible with recent U-Boot

On Wed, 25 Jul 2018 10:33:05 +0200
Ladislav Michl <ladis@...ux-mips.org> wrote:

> On Wed, Jul 25, 2018 at 10:18:28AM +0200, H. Nikolaus Schaller wrote:
> >   
> > > Am 25.07.2018 um 10:07 schrieb Ladislav Michl <ladis@...ux-mips.org>:
> > > 
> > > On Wed, Jul 25, 2018 at 08:58:41AM +0200, H. Nikolaus Schaller wrote:  
> > >> Vendor defined U-Boot has changed the partition scheme a while ago:
> > >> 
> > >> * kernel partition 6MB
> > >> * file system partition uses the remainder up to end of the NAND
> > >> * increased size of the environment partition (to get an OneNAND compatible base address)
> > >> * shrink the U-Boot partition
> > >> 
> > >> Let's be compatible (e.g. Debian kernel built from upstream).  
> > > 
> > > That, in fact, is breaking compatibility.  
> > 
> > With what? Nobody is using the old u-boot partition scheme any more
> > (it is >5 years old).
> >   
> > > So once you are touching this
> > > what about relying on partitioning provided by bootloader just to prevent
> > > something like this happening again?  
> > 
> > Well, we define what compatible means here (since we are the vendor).
> > And people complain with us. We simply recommend them to upgrade the
> > boot-loader.  
> 
> Fair enough. Suggestion was to remove partitioning scheme from DTB alltogether
> and let U-Boot provide one. But you being vendor you decide, of course :)
> (I'd use only two partitions: MLO and UBI, latter one with BCH8, and store
> everything in UBI volumes. That's a bit more flexible approach)
> 
hmm, so using mtdparts kernel commandline parameter? Somehow it sounds
to be sane to not have partition tables in kernel. What only is needed
is to have a nice transition scheme for systems in the wild, can
commandline mtdparts overwrite dtb? So dtb is a fallback?
But I think all that is a future improvement?

Regards,
Andreas

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ