linux-kernel - Re: Linux should define ENOTSUP

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: <a36005b50612061210q407ea90ew4a32328e65145bbf@mail.gmail.com>
Date:	Wed, 6 Dec 2006 12:10:08 -0800
From:	"Ulrich Drepper" <drepper@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"Samuel Thibault" <samuel.thibault@...-lyon.org>,
	"Arjan van de Ven" <arjan@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Linux should define ENOTSUP

On 12/6/06, H. Peter Anvin <hpa@...or.com> wrote:
> That's largely already the case, mostly because there is unfortunately
> still a fair bit of rubber-stamping Solaris going on.

Don't say that, Peter.

I'm working on the committee now for many years and got most changes I
(and those telling me their wishes) wanted through.  This is very much
a technically oriented working group, not political.  In fact, of the
regular members there are more with stakes in Linux than any of the
other OSes combined.  If there are problems people perceive they can
file bugs on the OpenGroup's site
(http://www.opengroup.org/austin/defectform.html) or tell me about it.

About the issue at hand: if the original poster would have taken the
time to investigate the issue he would have seen that this topic was
discussed (I think we handled it in September in Reading).  See

http://www.opengroup.org/austin/aardvark/latest/xbdbug2.txt

The statement about the interpretations track means that the change
will be made to the current standard, not only the next revision.

There is no need to change anything in kernel or libc.  Code using
both values in a switch statement is out of luck but a) this is really
really rare (nobody should reimplement strerror) and b) can be easily
fixed.
-
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/