| 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: Tue, 6 May 2008 09:42:25 -0700 From: "Luck, Tony" <tony.luck@...el.com> To: "Nadia Derbey" <Nadia.Derbey@...l.net> Cc: <linux-kernel@...r.kernel.org>, <y-goto@...fujitsu.com>, <akpm@...ux-foundation.org>, <linux-mm@...ck.org>, <containers@...ts.linux-foundation.org>, <matthltc@...ibm.com>, <cmm@...ibm.com> Subject: RE: [PATCH 1/8] Scaling msgmni to the amount of lowmem > Well, this printk had been suggested by somebody (sorry I don't remember > who) when I first submitted the patch. Actually I think it might be > useful for a sysadmin to be aware of a change in the msgmni value: we > have the message not only at boot time, but also each time msgmni is > recomputed because of a change in the amount of memory. If the message is directed at the system administrator, then it would be nice if there were some more meaningful way to show the namespace that is affected than just printing the hex address of the kernel structure. As the sysadmin for my test systems, printing the hex address is mildly annoying ... I now have to add a new case to my scripts that look at dmesg output for unusual activity. Is there some better "name for a namespace" than the address? Perhaps the process id of the process that instantiated the namespace??? -Tony -- 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