linux-kernel - Re: Unable to continue testing of 2.6.25

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: <20080217143851.c21a9cc4.pj@sgi.com>
Date:	Sun, 17 Feb 2008 14:38:51 -0600
From:	Paul Jackson <pj@....com>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	tilman@...p.cc, elendil@...net.nl, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org
Subject: Re: Unable to continue testing of 2.6.25

Adrian wrote:
> So let's fix the problem (kernel lacks functionality)

That's the problem as understood by Adrian.

I hear another problem as well ... 

Frans wrote:
> Please allow external users some decent period for transitioning. The 
> initial plan to "remove the old function in 2.6.27" was entirely sensible. 
> It's a pity it was not followed through.

That seems plain enough to me.  It's not just the lack of functionality,
but that such lack apparently happened with too little warning.

If this is a fair representation of what happened, then seems to me that
we could have left that EXPORT_UNUSED_SYMBOL(change_page_attr) in place
a bit longer.

Or at least, if we really did have to make Frans life difficult like
this, we could offer more appreciation for how things might look from
his perspective.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.940.382.4214
--
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/