| 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: Wed, 23 Jul 2008 16:53:07 +0400 From: Evgeniy Polyakov <johnpol@....mipt.ru> To: Jerome Arbez-Gindre <jeromearbezgindre@...il.com> Cc: linux-kernel@...r.kernel.org, deweerdt@...e.fr Subject: Re: New IDX in linux/connector.h ? Hi Jerome. On Wed, Jul 23, 2008 at 02:40:29PM +0200, Jerome Arbez-Gindre (jeromearbezgindre@...il.com) wrote: > Would it be possible to declare in linux/connector.h an IDX for the > BB, without any restriction on the VAL the BB could use? Sure. VAL (which is 'value' of course) is a private 'offset' inside given index (IDX), so when you register single IDX all corresponding VALs belong to the same user. And some side notes. I even wanted to have private indexes, i.e. those which are supposed to be used by out-of-the-tree code, and no in-kernel users would ever touch this numbers. You actually can use your own private numbers as long they do not correspond to currently loaded callbacks. Number of users in the header is actually a hint, it does not play any role at all as long as number of users is smaller than 32 (kernel stack allocates this bitmask by default even if number of users/sockets is smaller). There is also connector's itself own index (-1), used for requesting a notifications about new connector users registrations, it can be simply enough extended to provide dynamic index assignment. -- Evgeniy Polyakov -- 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