| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 6 Apr 2007 19:36:39 +0200 From: Ingo Molnar <mingo@...e.hu> To: John <linux.kernel@...e.fr> Cc: linux-kernel@...r.kernel.org, tglx@...esys.com Subject: Re: 2.6.20-rt8 patch tweaked for 2.6.20.5 * John <linux.kernel@...e.fr> wrote: > Hello, > > I've tweaked patch-2.6.20-rt8 so that it applies to 2.6.20.5 > > The unified diff is attached to this message. thanks - this is useful to those who are not that much on the bleeding edge. > I'd be happy to hear comments on what I've done wrong. > > 78 hunks had to be offset and 3 hunks had to be fuzzed. > > $ grep -B1 fuzz patch.log > patching file arch/ia64/kernel/iosapic.c > Hunk #3 succeeded at 469 with fuzz 2. > -- > patching file kernel/fork.c > Hunk #9 succeeded at 975 with fuzz 1. > -- > patching file kernel/sched.c > Hunk #46 succeeded at 3996 with fuzz 1. > > What is the fuzz value, exactly? it's harmless: when the 'patch' utility didnt find the 'context' of the patch chunk at its claimed position (because all patch chunks have precise coordinates of source code embedded), but finds them 'nearby' (or at least, somewhere in the file), it emits this reminder that the underlying code did change since the patch was generated. Generating a 'clean' patch will get rid of these messages. Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists