Re: [PATCH] coredump_filter: enable to change the default filter

Hidehiro Kawai
2008-12-26T09:45:51Z

KOSAKI Motohiro 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.
>
> FWIW, I think private namespace should have private settings framework.
> I don't like to make special private settings code in this patch.
>
> Yeah, defenitely we need to private settings for various reason, I agreed.
> but we also need consistent private settings rule and framework.
> otherwise, we will make various non consistent crap. maybe..

Anyway, as Andrew pointed out, current coredump filter doesn't
care for user mode helpers. So we need some sort of changes in
coredump filter so that users can change user mode helpers'
settings; use child_reapers setting as default (Roland's
suggestion) or use a boot parameter.

Thanks,
--
Hidehiro Kawai
Hitachi, Systems Development Laboratory
Linux Technology Center