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: <20120329075410.GC2098@minipsycho> Date: Thu, 29 Mar 2012 09:54:10 +0200 From: Jiri Pirko <jpirko@...hat.com> To: David Miller <davem@...emloft.net> Cc: netdev@...r.kernel.org, eric.dumazet@...il.com, bhutchings@...arflare.com, shemminger@...tta.com Subject: Re: [Q/RFC] BPF use in broader scope Thu, Mar 29, 2012 at 09:49:57AM CEST, davem@...emloft.net wrote: >From: Jiri Pirko <jpirko@...hat.com> >Date: Thu, 29 Mar 2012 09:44:43 +0200 > >> Here are proposed things to be done: >> 1) introduce in-kernel api for creating sk-unattached filters (I have >> the patch cooked up already) >> >> 2) extend current BPF machine to allow XOR operation. Not sure if this >> is doable or what the best of doing this is. >> >> 3) add possibility to pass some data to the machine via >> pre-filling "Scratch Memory Store". I think this can be done easily >> moving "u32 mem[BPF_MEMWORDS];" to bpf_func caller and pass it as the >> second function parameter. That should not break anything. >> >> Then the computed hash can be either stored into Scratch memory or returned >> directly (where ordinary sk filters return len). >> >> Does this seems reasonable? Thoughts, comments? > >No fundamental objections, but we have all of these JITs now to >update when adding new operations or semantics, so be careful. Yep, I'm aware. I must admit that the JIT code scares me a litte :( -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists