Hello, I always used skas3 patch on my systems, but, since SKAS4 supports also x86_64 architectures I think it's time to try it on my AMD64. I'm using Gentoo Linux Kernel 2.6.23-r8. I copied the patch into a text file and I did as follows from the kernel root directory:
cat ../skas4-2.6.patch | patch -p1 --dry-run I get these messages: ========================================================== patching file arch/um/include/as-layout.h Hunk #1 FAILED at 17. Hunk #2 FAILED at 28. 2 out of 2 hunks FAILED -- saving rejects to file arch/um/include/as-layout.h.rej patching file arch/um/include/os.h Hunk #1 succeeded at 173 (offset 5 lines). patching file arch/um/include/siginfo_segv.h patching file arch/um/include/skas/mm_id.h patching file arch/um/include/skas/skas.h Hunk #1 FAILED at 6. 1 out of 1 hunk FAILED -- saving rejects to file arch/um/include/skas/skas.h.rej patching file arch/um/include/skas_ptrace.h patching file arch/um/kernel/ptrace.c Hunk #1 succeeded at 213 (offset 21 lines). Hunk #2 succeeded at 307 (offset 15 lines). patching file arch/um/kernel/reboot.c Hunk #1 FAILED at 11. 1 out of 1 hunk FAILED -- saving rejects to file arch/um/kernel/reboot.c.rej patching file arch/um/kernel/skas/mmu.c Hunk #1 FAILED at 65. Hunk #2 FAILED at 104. Hunk #3 FAILED at 153. 3 out of 3 hunks FAILED -- saving rejects to file arch/um/kernel/skas/mmu.c.rej patching file arch/um/kernel/skas/process.c Hunk #1 succeeded at 123 with fuzz 2 (offset 114 lines). Hunk #2 FAILED at 163. 1 out of 2 hunks FAILED -- saving rejects to file arch/um/kernel/skas/process.c.rej patching file arch/um/kernel/syscall.c Hunk #1 succeeded at 161 (offset 10 lines). patching file arch/um/kernel/um_arch.c Hunk #1 FAILED at 271. 1 out of 1 hunk FAILED -- saving rejects to file arch/um/kernel/um_arch.c.rej patching file arch/um/os-Linux/skas/mem.c Hunk #1 succeeded at 5 with fuzz 2 (offset -1 lines). Hunk #2 succeeded at 27 with fuzz 2 (offset 4 lines). Hunk #3 FAILED at 46. Hunk #4 FAILED at 119. Hunk #5 FAILED at 197. 3 out of 5 hunks FAILED -- saving rejects to file arch/um/os-Linux/skas/mem.c.rej patching file arch/um/os-Linux/skas/process.c Hunk #1 succeeded at 3 with fuzz 2. Hunk #2 FAILED at 94. Hunk #3 FAILED at 227. Hunk #4 FAILED at 268. Hunk #5 succeeded at 358 with fuzz 2 (offset -23 lines). Hunk #6 FAILED at 380. Hunk #7 succeeded at 452 (offset -22 lines). Hunk #8 FAILED at 656. 5 out of 8 hunks FAILED -- saving rejects to file arch/um/os-Linux/skas/process.c.rej patching file arch/um/os-Linux/start_up.c Hunk #1 FAILED at 3. Hunk #2 FAILED at 26. Hunk #3 succeeded at 164 (offset 18 lines). Hunk #4 succeeded at 203 (offset 18 lines). Hunk #5 succeeded at 384 (offset 19 lines). Hunk #6 succeeded at 395 (offset 19 lines). Hunk #7 succeeded at 415 (offset 19 lines). Hunk #8 succeeded at 427 (offset 19 lines). Hunk #9 FAILED at 447. Hunk #10 FAILED at 482. Hunk #11 succeeded at 523 with fuzz 2 (offset 25 lines). 4 out of 11 hunks FAILED -- saving rejects to file arch/um/os-Linux/start_up.c.rej patching file arch/um/sys-i386/ldt.c Hunk #1 succeeded at 511 with fuzz 2 (offset 75 lines). patching file arch/um/sys-i386/stub.S Hunk #1 FAILED at 1. 1 out of 1 hunk FAILED -- saving rejects to file arch/um/sys-i386/stub.S.rej patching file arch/um/sys-x86_64/stub.S Hunk #1 FAILED at 1. 1 out of 1 hunk FAILED -- saving rejects to file arch/um/sys-x86_64/stub.S.rej patching file arch/um/sys-x86_64/syscall_table.c patching file arch/um/sys-x86_64/syscalls.c Hunk #1 FAILED at 30. 1 out of 1 hunk FAILED -- saving rejects to file arch/um/sys-x86_64/syscalls.c.rej can't find file to patch at input line 1698 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff --git a/arch/x86/ia32/ia32_signal.c b/arch/x86/ia32/ia32_signal.c |index 6ea19c2..2f74adf 100644 |--- a/arch/x86/ia32/ia32_signal.c |+++ b/arch/x86/ia32/ia32_signal.c -------------------------- File to patch: ======================================================== Here I pressed CTRL+C to interrupt the --dry-run patching test. So I have two questions: 1) Can I apply that patch to a 2.6.23 kernel? 2) Why these two rows include "a/" and "/b" at the beginning? Actually in my kernel tree, doesn't exist any a or b directory, so that's the reason why it asks me what file to patch. Maybe other messages I reported above are useful to say where the problem is. I see a lot of "FAILED" and that seems nothing good. What's wrong? Thank you. Best Regards, Flavio ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
