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: <1391974709.25855.3.camel@x220>
Date:	Sun, 09 Feb 2014 20:38:29 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Richard Weinberger <richard@....at>
Cc:	David Howells <dhowells@...hat.com>,
	Koichi Yasutake <yasutake.koichi@...panasonic.com>,
	"moderated list:PANASONIC MN10300..." <linux-am33-list@...hat.com>,
	open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 24/28] Remove DEPRECATED

On Sun, 2014-02-09 at 19:48 +0100, Richard Weinberger wrote:
> The symbol is an orphan, get rid of it.
> 
> Signed-off-by: Richard Weinberger <richard@....at>
> ---
>  arch/mn10300/Kconfig.debug | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/mn10300/Kconfig.debug b/arch/mn10300/Kconfig.debug
> index 94efb3e..af18047 100644
> --- a/arch/mn10300/Kconfig.debug
> +++ b/arch/mn10300/Kconfig.debug
> @@ -32,7 +32,7 @@ config KPROBES
>  
>  config GDBSTUB
>  	bool "Remote GDB kernel debugging"
> -	depends on DEBUG_KERNEL && DEPRECATED
> +	depends on DEBUG_KERNEL

But now you've enabled a lot of stuff that, as far as I can tell, could
not have been built since v2.6.39.

The proper fix would be to remove GDBSTUB and everything that depends on
it. I tried to do that once and it turned out to be much more work than
I expected. So perhaps we should just do s/DEPRECATED/BROKEN/ and let
the mn10300 maintainers deal with this.
 
>  	select DEBUG_INFO
>  	select FRAME_POINTER
>  	help


Paul Bolle

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ