| 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: <49547836.7040907@hitachi.com> Date: Fri, 26 Dec 2008 15:22:46 +0900 From: Hidehiro Kawai <hidehiro.kawai.ez@...achi.com> To: Roland McGrath <roland@...hat.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>, linux-kernel@...r.kernel.org, yumiko.sugita.yf@...achi.com, satoshi.oshima.fk@...achi.com Subject: Re: [PATCH] coredump_filter: enable to change the default filter Hi, I'm sorry for late reply. Roland McGrath wrote: >>However, we would need a special care for PID namespace if we use >>init's coredump_filter as default. For a process with new PID >>namespace and new /proc, writing to /proc/1/coredump_filter doesn't >>mean changing default, although it's not a usual operation. > > I'd figured that private PID namespaces with their own init would want > their own private settings for this default too. Probably it's true, but I'm not sure if having coredump_filter have two means is acceptable. init in a private PID namespace can die and dump a core file. So its coredump_filter has two means; default setting for the namespace and setting for itself. Thanks, -- Hidehiro Kawai Hitachi, Systems Development Laboratory Linux Technology Center -- 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