lcall disappeared? kernel CVS destabilized?
I'm porting the seccomp patch to 2.6.10, do you have an idea where lcall (i.e. call gates for binary compatibility with other OS) went? I can't find it anywhere. Looks like it was dropped but I must be sure of that, and especially I must be sure that you don't add it again without me noticing that I had to patch it ;). Is lcall definitely dead code that I can forget about or am I missing something? Thanks.
Kernel CVS is broken here, it doesn't even show me the changeset where lcall disappeared, this returns nothing obvious:
cvsps -g -r v2_6_8 -f arch/i386/kernel/entry.S
If I use cvsps -x --bkcvs the changesets are screwed.
Note that the entry.S of the kernel CVS has not the lcall, it's magically forgetting to show me a chageset, and I doubt cvsps is to blame here, since it was working well for a long time before the thing destabilized.
Can somebody confirm the kernel CVS is unstable or am I the only one having deep troubles?
Quoted 3 lines · Andrea Arcangeli
I'm porting the seccomp patch to 2.6.10, do you have an idea where lcall
(i.e. call gates for binary compatibility with other OS) went?
Was removed on October 18.
Quoted 8 lines · Andrew Morton
Quoted 3 lines · Andrea Arcangeli
I'm porting the seccomp patch to 2.6.10, do you have an idea where lcall
(i.e. call gates for binary compatibility with other OS) went?Was removed on October 18.
Ok, thanks to both for the confirmation ;).
Quoted 6 lines · Andrea Arcangeli
I'm porting the seccomp patch to 2.6.10, do you have an idea where lcall (i.e. call gates for binary compatibility with other OS) went? I can't find it anywhere. Looks like it was dropped but I must be sure of that, and especially I must be sure that you don't add it again without me noticing that I had to patch it ;). Is lcall definitely dead code that I can forget about or am I missing something? Thanks.
hch removed it some time ago because nobody used it anymore (Linux ABI is not supported on 2.6) and it showed some potential security issues
-Andi