<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 24, 2017 at 5:27 PM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, 2017-04-24 at 15:56 -0400, Bruce Ashfield wrote:<br>
><br>
><br>
> On Mon, Apr 24, 2017 at 9:54 AM, Bruce Ashfield <bruce.ashfield@gmail<br>
<div><div class="gmail-h5">> .com> wrote:<br>
> ><br>
> ><br>
> > On Mon, Apr 24, 2017 at 9:39 AM, Martin Jansa <martin.jansa@gmail.c<br>
> > om> wrote:<br>
> > > I'm still seeing this with your "kernel-yocto/kern-tools: fix<br>
> > > do_validate_branches clean stage" patch applied:<br>
> > ><br>
> > ><br>
> > > | DEBUG: Executing shell function do_patch<br>
> > > | ERROR: Could not apply patches for qemux86.<br>
> > > | ERROR: Patch failures can be resolved in the linux source<br>
> > > directory work-shared/qemux86/kernel-<wbr>source)<br>
> > > | <br>
> > > | [ERROR] Can't find patch dir at .kernel-meta/<br>
> > > | usage: kgit s2q<br>
> > > | ERROR: Function failed: do_patch (log file is located at linux-<br>
> > > yocto/1_4.10.9+gitAUTOINC+<wbr>ad2e885015_fe0fb8da3d-<br>
> > > r0/temp/log.do_patch.44497)<br>
> > > NOTE: recipe linux-yocto-<br>
> > > 1_4.10.9+gitAUTOINC+<wbr>ad2e885015_fe0fb8da3d-r0: task do_patch:<br>
> > > Failed<br>
> > ><br>
> > Well bugger.<br>
> ><br>
> > I'll start another set of builds.<br>
> ><br>
> I had this on a build loop all day without any luck. I also enlisted<br>
> a few others around the office<br>
> to build master and see if they could cause an issue .. again, no<br>
> luck.<br>
><br>
> Richard/Ross: are you seeing this same thing on the autobuilder ?<br>
><br>
> There's some incantation or config that I'm missing, I assume this is<br>
> a straight qemux86 config<br>
> with a bitbake of something like core-image-minimal ?<br>
<br>
</div></div>We're not seeing this on the autobuilders. I do suspect something in<br>
the handling of extra patches or cfg fragments from SRC_URI if I had to<br>
guess. That certainly was the trigger last time I saw this.<br></blockquote><div><br></div><div>Yah, that's the kicker, I'm still carrying your patch for binfmt_elf, and I added two of my own</div><div>+ config fragments, and I can't trigger anything.</div><div><br></div><div>Bruce</div><div><br></div><div>gmail garbled and and paste below:</div><div><br><div>-------------------</div></div><div><br></div><div><br></div><div>% git describe <br></div><div>
<p class="gmail-p1"><span class="gmail-s1">v4.10.9-378-gff739b66b0bc</span></p></div><div>
<p class="gmail-p1"><span class="gmail-s1"><br></span></p><p class="gmail-p1"><span class="gmail-s1">% git whatchanged</span></p><p class="gmail-p1"><span class="gmail-s1">commit ff739b66b0bc5cd65bcc26d4556736309f4b180c</span></p><p class="gmail-p1">Author: Bruce Ashfield <<a href="mailto:bruce.ashfield@windriver.com">bruce.ashfield@windriver.com</a>></p><p class="gmail-p1">Date: Fri Jul 8 11:32:11 2016 -0400</p>
<p class="gmail-p3"><span class="gmail-s1"></span><br></p>
<p class="gmail-p2"><span class="gmail-s1"> makefile: comment two</span></p>
<p class="gmail-p3"><br></p><p class="gmail-p3"> Signed-off-by: Bruce Ashfield <<a href="mailto:bruce.ashfield@windriver.com">bruce.ashfield@windriver.com</a>><br></p>
<p class="gmail-p3"><span class="gmail-s1"></span><br></p>
<p class="gmail-p2"><span class="gmail-s1">:100644 100644 a027ca58d9ff... 2402e34170b5... M Makefile</span></p>
<p class="gmail-p3"><span class="gmail-s1"></span><br></p>
<p class="gmail-p1"><span class="gmail-s1">commit 238fd7383ebb99f080febdfb31d680b43fbb7438</span></p>
<p class="gmail-p2"><span class="gmail-s1">Author: Bruce Ashfield <<a href="mailto:bruce.ashfield@windriver.com">bruce.ashfield@windriver.com</a>></span></p>
<p class="gmail-p2"><span class="gmail-s1">Date: Fri Jul 8 11:31:34 2016 -0400</span></p>
<p class="gmail-p3"><span class="gmail-s1"></span><br></p>
<p class="gmail-p2"><span class="gmail-s1"> makefile: comment one</span></p>
<p class="gmail-p3"><span class="gmail-s1"> </span></p>
<p class="gmail-p2"><span class="gmail-s1"> Signed-off-by: Bruce Ashfield <<a href="mailto:bruce.ashfield@windriver.com">bruce.ashfield@windriver.com</a>></span></p>
<p class="gmail-p3"><span class="gmail-s1"></span><br></p>
<p class="gmail-p2"><span class="gmail-s1">:100644 100644 3d994e6df89a... a027ca58d9ff... M Makefile</span></p>
<p class="gmail-p3"><span class="gmail-s1"></span><br></p>
<p class="gmail-p1"><span class="gmail-s1">commit 5376026f981849bee7d1789c67b81e1e758ef6f0</span></p>
<p class="gmail-p2"><span class="gmail-s1">Author: invalid_git config <unknown@unknown></span></p>
<p class="gmail-p2"><span class="gmail-s1">Date: Mon Apr 24 20:48:24 2017 -0400</span></p>
<p class="gmail-p3"><span class="gmail-s1"></span><br></p>
<p class="gmail-p2"><span class="gmail-s1"> The kernel makes the assumption that all PT_LOAD sections are continous, at</span></p>
<p class="gmail-p2"><span class="gmail-s1"> least to the point where PT_PHDR is contained. If there are holes between</span></p>
<p class="gmail-p2"><span class="gmail-s1"> the PT_LOAD sections, the calculation load_addr + exec->e_phoff fails to</span></p>
<p class="gmail-p2"><span class="gmail-s1"> correctly locate the phdrs.</span></p>
<p class="gmail-p3"><span class="gmail-s1"> </span></p>
<p class="gmail-p2"><span class="gmail-s1"> This change notices where phdrs are located in some other PT_LOAD section</span></p>
<p class="gmail-p2"><span class="gmail-s1"> other than the first one and corrects the offsets used.</span></p>
<p class="gmail-p3"><span class="gmail-s1"> </span></p>
<p class="gmail-p2"><span class="gmail-s1"> This is useful where userspace wants to rewrite elf files but can't guarantee</span></p>
<p class="gmail-p2"><span class="gmail-s1"> that all PT_LOAD sections are continuous without holes without potentially</span></p>
<p class="gmail-p2"><span class="gmail-s1"> creating large holes in the binaries. I was unable to find any ELF spec</span></p>
<p class="gmail-p2"><span class="gmail-s1"> which requires continuous PT_LOAD sections or that PT_PHDR be in the first</span></p>
<p class="gmail-p2"><span class="gmail-s1"> PT_LOAD section.</span></p>
<p class="gmail-p3"><span class="gmail-s1"> </span></p>
<p class="gmail-p2"><span class="gmail-s1"> Signed-off-by: Richard Purdie <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>></span></p>
<p class="gmail-p3"><span class="gmail-s1"></span><br></p>
<p class="gmail-p2"><span class="gmail-s1">:100644 100644 422370293cfd... 392dab375b63... M fs/binfmt_elf.c</span></p></div><div>-------------------</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Cheers,<br>
<br>
Richard<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"</div>
</div></div>