linux-kernel - Re: New IDX in linux/connector.h ?

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a1d7a2f20807230645t461265ecu2d9e7f70484a8c91@mail.gmail.com>
Date:	Wed, 23 Jul 2008 15:45:09 +0200
From:	"Jerome Arbez-Gindre" <jeromearbezgindre@...il.com>
To:	"Evgeniy Polyakov" <johnpol@....mipt.ru>
Cc:	linux-kernel@...r.kernel.org, deweerdt@...e.fr
Subject: Re: New IDX in linux/connector.h ?

Hi Evgeniy,

>> 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.

I meant:

 diff --git a/include/linux/connector.h b/include/linux/connector.h
index 96a89d3..361996c 100644
--- a/include/linux/connector.h
+++ b/include/linux/connector.h
@@ -38,6 +38,7 @@
 #define CN_W1_VAL			0x1
 #define CN_IDX_V86D			0x4
 #define CN_VAL_V86D_UVESAFB		0x1
+#define CN_IDX_BB			0x5

 #define CN_NETLINK_USERS		5

> 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.

So which numbers am I suppose to use ... taking account that BB will
probably stay for a long time out-of-the-tree ?

Thanks

              Jerome Arbez-Gindre
--
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/