[U-Boot] [PATCH 01/15] sandbox: Unprotect DATA regions in bus tests

Simon Glass sjg at chromium.org
Wed Oct 17 18:19:36 UTC 2018


Hi Alex,

On 16 October 2018 at 08:48, Alexander Graf <agraf at suse.de> wrote:
>
>
>
> On 29.09.18 20:29, Simon Glass wrote:
> > Hi Alex,
> >
> > On 23 September 2018 at 23:34, Alexander Graf <agraf at suse.de> wrote:
> >>
> >>
> >> On 24.09.18 00:47, Simon Glass wrote:
> >>> On my Ubuntu 18.04.1 machine two driver-model bus tests have started
> >>> failing recently. The problem appears to be that the DATA region of the
> >>
> >> Are you sure it's .data and not .rodata?
> >>
> >> The linker script should really put all those lists into its own
> >> section, so I'm not sure how you end up with them getting write
> >> protected. Can you please run
> >
> > It doesn't happen on my normal computer, but I upgraded one to Ubuntu
> > 18.04 and noticed this. It's a bit odd, but I wonder if it is deciding
> > that the section name means it is rodata?
> >
> >>
> >>   $ objdump -h u-boot
> >>
> >> on your broken binary? Also do
> >>
> >>   $ nm u-boot | grep .u_boot_list
> >>
> >> so we can correlate whether the symbols ended up in the correct section.
> >
> > Yes, please see below.
>
> All the list symbols are in the u_boot_list section which is writable. I
> don't know why it wouldn't work.
>
> Have you figured out why it breaks for you?

No, unfortunately not. It is a bit of a mystery!

Regards,
Simon


More information about the U-Boot mailing list