Thanks for the pointers, guys. It took a while for me to figure out what
got wrong to foul up UML, but the bug and fix are trivial (posting now).
Some of the testing I thought had got done clearly wasn't done, since
PTRACE_SETREGS was 100% busticated for 32-bit processes calling ptrace on
x86_64 k
On Thu, Feb 21, 2008 at 06:20:23PM +0100, Miklos Szeredi wrote:
> Bisected it down to
>
> good e7b5e11eaaa8ef93a34e68016de51152d0d62911
> bad bde6f5f59c2b2b48a7a849c129d5b48838fe77ee
>
> I strongly suspect it's one of the ptrace cleanup patches. Roland,
> could you please have a look?
I agree.
> > > > - UML doesn't boot: guest is 2.6.24-mm1 also, haven't tried any
> > > >other. Same guest boots fine on 2.6.24 host.
> > >
> > > What does it do?
> >
> > See below.
>
> This bug seems to have made it to mainline as well, starting with
> -rc1. Any ideas? Should I start bisecting?
> > > - UML doesn't boot: guest is 2.6.24-mm1 also, haven't tried any
> > >other. Same guest boots fine on 2.6.24 host.
> >
> > What does it do?
>
> See below.
This bug seems to have made it to mainline as well, starting with
-rc1. Any ideas? Should I start bisecting?
Thanks,
Miklos
>
4 matches
Mail list logo
