| 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, 5 Sep 2011 13:39:03 -0700 From: Arjan van de Ven <arjan@...radead.org> To: Vladimir Zapolskiy <vz@...ia.com> Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <peterz@...radead.org>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [PATCH] sched: share task comm length value to userspace On Mon, 05 Sep 2011 23:17:05 +0300 Vladimir Zapolskiy <vz@...ia.com> wrote: > but eventually having that value in > userspace is really desirable. However in assumption that this value > is preserved fixed and won't be changed in reasonable perspective, > the presented approach becomes the most evident and simple. yeah if it would never change, your change would be the most simple. but I really don't want to pin that thing down.... > > > > > If we need to export this, we should export it in /proc or /sys > > somewhere as a dynamic value..... > > > Let's do it in a proper way. What's the common practice to export > such limit values? I suppose via /proc/sys/kernel, please correct me, > if I'm wrong. that or /sys/kernel personally I like /proc/sys/kernel for this kind of thing more, but... ... others might disagree. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org -- 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