On 07/11/16 17:09, Tejun Heo wrote: > Hello, > > On Mon, Jul 11, 2016 at 02:14:31PM +0300, Topi Miettinen wrote: >> [ 28.443674] audit: type=1327 audit(1468234333.144:520): proctitle=6D6B6E6F64002F6465762F7A5F343639006300310032 >> [ 28.465888] audit: type=1330 audit(1468234333.144:520): cap_used=0000000008000000 >> [ 28.482080] audit: type=1331 audit(1468234333.144:520): cgroups=:/test; > > Please don't put additions of the two different audit types into one > patch and I don't think the cgroup audit logging makes much sense. > Without logging all migrations, it doesn't help auditing all that > much. Also, printing all cgroup membership like that can be > problematic for audit it can be arbitrarily long. > > Thanks. > It's really critical to be able to associate a task in the logs to cgroups which were valid that time. Or can we infer somehow what cgroups a task was taking part, long time after task exit? Perhaps task cgroup membership changes and changes in available cgroups should be logged too? Some kind of cgroup IDs could be logged instead of long paths. Then these IDs should be reliably resolvable to paths offline somehow. How usual migrations between cgroups are? Why would a task ever move from (say) systemd/system.slice/smartd.service to anywhere else? -Topi -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
