| 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
| ||
|
Message-ID: <460291DE.8090403@slax.org> Date: Thu, 22 Mar 2007 15:25:34 +0100 From: Tomas M <tomas@...x.org> To: linux-kernel@...r.kernel.org Subject: Re: max_loop limit > You might want a more radical patch : I agree that my patch is not the perfect solution for max_loop problem. But it nearly doubles max_loop for me (using 386 arch) and moreover it is a FIX for incorrect implementation in kernel IMHO. So I can see REASON to include it in Kernel. Do I cry at the correct tomb? :) > > Instead of using : > :: > Switch to : > :: I'm not any professional kernel hacker, so I don't understand the mysteries regarding ** (pointers to pointers?). Is there anyone who could provide CLEAN patch for loop.c, which would raise the max_loop limit to (at least) 1024 and which would be ACCEPTED to mainline kernel any soon? I'm offering MONEY for this task. Let's say $256 ;-) I hope I didn't offend anyone by this offer. Tomas M slax.org - 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