linux-kernel - 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-next>] [day] [month] [year] [list]

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

Hi Evgeniy,

Nowadays, I'm working on a free software framework called TSP
(https://savannah.nongnu.org/p/tsp)
one of its components is a Blackboard (Aka BB).

It is simply a structured shared memory with named fields.
At the beginning, the BB was used to share/export data between two or
more userspace processes.
The blackboard also comes with messaging capabilities (which allows to
synchronize processes).

I'm working on a kernel port of the BB... and particularly on the
messaging feature.

My implementation is thus a user of your connector API

My request is the following:

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?

We are willing to include the BB in-tree but this needs to be
discussed (in terms of usefulness) as the current kernel
implementation shares lots of code with the userspace implementations.

Thanks

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