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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 18 Sep 2017 09:21:35 -0700 From: Christoph Hellwig <hch@...radead.org> To: Shivasharan Srikanteshwara <shivasharan.srikanteshwara@...adcom.com> Cc: Christoph Hellwig <hch@...radead.org>, shuwang@...hat.com, Kashyap Desai <kashyap.desai@...adcom.com>, Sumit Saxena <sumit.saxena@...adcom.com>, jejb@...ux.vnet.ibm.com, martin.petersen@...cle.com, "PDL,MEGARAIDLINUX" <megaraidlinux.pdl@...adcom.com>, linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org, chuhu@...hat.com, yizhan@...hat.com, catalin.marinas@....com Subject: Re: [PATCH V2] megaraid: kmemleak: Track page allocation for fusion Oh, I missed log_to_span. Well, in that case log_to_span is _the_ candidate for moving into a separate allocation. And in fact you're probably better off by using a sensible data structure for it, e.g. a radix tree.
Powered by blists - more mailing lists