| 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: Mon, 05 Nov 2007 17:32:32 +0100 From: Jan Blunck <jblunck@...e.de> To: Linux-Kernel Mailinglist <linux-kernel@...r.kernel.org>, Christoph Hellwig <hch@...radead.org>, Andrew Morton <akpm@...ux-foundation.org> Subject: [PATCH 0/9] struct path related cleanups of d_path() code (V2) Andrew, please apply this series to -mm. I just added the seq_file patch, another nfsd cleanup and changed the patch order. This patch series changes d_path() to take a struct path argument. The existing users are changed to give struct path more deeply into the call chain. In some cases I replaced existing <dentry,vfsmount> pairs and embed a struct path instead. Thanks, Jan >>one-less-parameter-to-__d_path.patch<< One less parameter to __d_path >>d_path-kerneldoc_cleanup.diff<< d_path: kerneldoc cleanup >>d_path-Use_struct_path_in_struct_avc_audit_data.diff<< d_path: Use struct path in struct avc_audit_data >>d_path-Make_proc_get_link_use_a_struct_path_argument.diff<< d_path: Make proc_get_link() use a struct path argument >>d_path_Make_get_dcookie_use_a_struct_path_argument.diff<< d_path: Make get_dcookie() use a struct path argument >>nfsd-svc_export_use_struct_path.diff<< Use struct path in struct svc_export >>nfsd-svc_expkey_use_struct_path.diff<< Use struct path in struct svc_expkey >>d_path-Make_seq_path_use_a_struct_path_argument.diff<< d_path: Make seq_path() use a struct path argument >>d_path-use_struct_path.diff<< d_path: Make d_path() use a struct path - 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