linux-kernel - Re: [PATCH] posix_types.h: Cleanup stale _

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]

Date:	Wed, 25 Jul 2012 21:42:14 -0400
From:	Josh Boyer <jwboyer@...hat.com>
To:	Jonathan Nieder <jrnieder@...il.com>
Cc:	Ben Hutchings <ben@...adent.org.uk>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>, law@...hat.com,
	stable@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] posix_types.h: Cleanup stale __NFDBITS and related
 definitions

On Wed, Jul 25, 2012 at 08:33:22PM -0500, Jonathan Nieder wrote:
> Hi,
> 
> Josh Boyer wrote:
> 
> > Indeed.  However, I believe Linus pointed out that even before
> > 8b3d1cda4f5f the macros that were removed weren't actually used.
> > It's likely safe to go back further than just 3.4.
> >
> > I'll verify again in the morning and include the furthest back we could
> > remove these.  For now, let's go with what you suggest to be safe.
> 
> I may be in the minority in having this view or missing a subtlety,
> but shouldn't the question be the furthest back we need to remove
> these rather than the furthest back we could?

That should be the question, yes.  The answer is:

However far back people wish to use older stable kernel-headers to build
applications against newer glibc.

It isn't a clear answer.  Some people stick with older kernels while
they update their userspace.  I was thinking along the lines of the 3.0
kernel being the oldest I'd check for but if people think we shouldn't
bother than that's fine by me.

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