| 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: <AANLkTimCBX7FSBByeOmCp_ofYvmFeE8OF85OzB5tfjhw@mail.gmail.com> Date: Mon, 22 Nov 2010 19:10:53 -0800 From: Tony Luck <tony.luck@...el.com> To: Jim Keniston <jkenisto@...ux.vnet.ibm.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [RFC] persistent store On Mon, Nov 22, 2010 at 5:37 PM, Tony Luck <tony.luck@...el.com> wrote: > Yes - I assume here that the last "data_size" bytes will be enough > to be useful. But in your case it most likely won't be. You could > lie about how much space you allow and then include some oops > parsing code to get the vital bits out of what is passed to you. Not > pretty - but it would work. If there are many such devices with limited > capacity, then it would make sense to include this parsing code > in this generic layer. Sorry - finding the good bits from the console log is architecture dependent ... so it can't be done (easily) in the generic code. -Tony -- 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