From: Alexander Gabert <pappy@gentoo.org>
To: Arjan van de Ven <arjan@infradead.org>,
libc-alpha@sourceware.org, linux-kernel@vger.kernel.org,
hardened@gentoo.org
Subject: Re: AT_ENTROPY1 and AT_ENTROPY2 values for include/linux/auxvec.h
Date: Mon, 18 Jun 2007 12:36:10 +0200 [thread overview]
Message-ID: <4676601A.7070209@gentoo.org> (raw)
In-Reply-To: <1182130680.22999.13.camel@laptopd505.fenrus.org>
Arjan van de Ven schrieb:
>> Hence the config option for the kernel- it's philosophy at Gentoo to
>> make choices available to users how they want their systems to behave,
>> even on the expense of added complexity and need to "understand" how
>> things work in the first place.
>>
>
> While I am not opposed to choice, I am opposed to having too finegrained
> kernel config options. In your view, every single kernel patch would be
> a config option... I much rather have config options for "important" big
> changes, not for something this small. Another argument is that this
> kind of userspace interface is better off being always there or never;
> making this variable serves no-one.
>
>
>
>
Hi again,
as said, i'm not voting for getting the specific example patch into
kernel source.
All i came for and would like to see is the two numbers into the
upstream header file to avoid future namespace clashes (as said in the
original mail).
I honestly don't know how to follow the discussion to implement this
kind of entropy given via auxv to userland- if you (the kernel devs)
think it makes sense the way you want it you as upstream devs can do it
all the way you like it- i can always change it with a patch for my own
needs in my own sources. I can't say anything at all about all of this
because i don't know what is important from your point of view as kernel
maintainers and what is not. I understand your concerns and know that
we are talking from different perspectives, thus it is probably normal
that our interests and technical solutions vary.
However, as said, the only thing important for me is to not use
"arbitrary" chosen numbers for the AT_ENTROPY1 and 2 values and later
have problems when my "private" numbers suddenly are assigned to a
different thing by "official" kernel devs. That would be bad for me and
this is what i want to avoid in the first place.
So please tell me what i can do about the requirements and the time and
what the usual process is for asking how to get the numbers into the
kernel so i can start using them for my own work.
Thanks in advance,
Alex
next prev parent reply other threads:[~2007-06-18 10:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 23:40 AT_ENTROPY1 and AT_ENTROPY2 values for include/linux/auxvec.h Alexander Gabert
2007-06-18 1:06 ` Arjan van de Ven
2007-06-18 1:28 ` Alexander Gabert
2007-06-18 1:38 ` Arjan van de Ven
2007-06-18 10:36 ` Alexander Gabert [this message]
2007-06-20 15:34 ` [PATCH] get_random_long() and AT_ENTROPY for auxv, kernel 2.6.21.5 Alexander Gabert
2007-06-20 15:38 ` Arjan van de Ven
2007-06-20 16:39 ` Linus Torvalds
2007-06-20 17:04 ` Eric Dumazet
2007-06-20 20:30 ` Matt Mackall
2007-06-24 17:45 ` Alexander Gabert
2007-06-25 3:45 ` Matt Mackall
2007-06-25 4:43 ` Arjan van de Ven
2007-06-25 5:12 ` Matt Mackall
2007-06-25 7:09 ` Jakub Jelinek
2007-06-25 15:02 ` Alexander Gabert
2007-06-25 15:20 ` Matt Mackall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4676601A.7070209@gentoo.org \
--to=pappy@gentoo.org \
--cc=arjan@infradead.org \
--cc=hardened@gentoo.org \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).