| 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, 18 Sep 2006 11:41:06 -0400 From: "Dmitry Torokhov" <dmitry.torokhov@...il.com> To: "Rolf Eike Beer" <eike-kernel@...tec.de> Cc: "Greg KH" <greg@...ah.com>, linux-kernel@...r.kernel.org Subject: Re: Exporting array data in sysfs On 9/18/06, Rolf Eike Beer <eike-kernel@...tec.de> wrote: > Dmitry Torokhov wrote: > > On 9/18/06, Rolf Eike Beer <eike-kernel@...tec.de> wrote: > >>Dmitry Torokhov wrote: > > >>> http://www.ussg.iu.edu/hypermail/linux/kernel/0503.2/1155.html > > >> The limitation to 999 entries should go. > > > > It is not really a limitation but rather a safeguard. Do you really > > expect to have arrays with that many attributes? > > At least I don't know how much they will be. If the user wants to do crazy > things... :) I'm currently hacking on a store_n implementation, perhaps I'll > be able to show some code tomorrow. > I do not think you shoudl allow user do crazy things. The memory is kmalloced so there naturally a limit on number of attrinutes that can be created. And I am not sure abot usefulness of resizing form usespace. Could you give me an example of a user who needs dynamic attribute arrays? -- Dmitry - 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