| 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: Wed, 30 Oct 2013 06:19:42 -0700 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: Peng Tao <bergwolf@...il.com> Cc: linux-kernel@...r.kernel.org, Andreas Dilger <andreas.dilger@...el.com> Subject: Re: [PATCH 1/4] staging/lustre/llite: cache jobid in lu_env On Wed, Oct 30, 2013 at 07:30:33PM +0800, Peng Tao wrote: > We will switch to find jobid from /proc/self/environ and we need an > extra memory copy to do it, so let's cache it in lu_env. > It is then copied from lu_env to ll_inode_info upon every read/write. What does this mean? And you better not be reading proc values from within the kernel... greg k-h -- 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