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] [day] [month] [year] [list]
Date:	Tue, 17 Aug 2010 12:35:34 -0400
From:	Mike Frysinger <vapier.adi@...il.com>
To:	Philippe De Muyter <phdm@...qel.be>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] m68k{nommu}/blackfin : remove old assembler-only flags
 bit definitions.

On Tue, Aug 17, 2010 at 11:28, Philippe De Muyter wrote:
> Long ago, PT_TRACESYS_OFF and friends were introduced as hard defines
> to avoid straight constants in assembler parts of linux m68k.
> They are not used anymore, and were not updated to follow changes
> in linux kernel.  Remove them.  When similar constants are needed,
> they are now generated using asm-offsets.c.
>
> --- a/arch/blackfin/include/asm/entry.h
> +++ b/arch/blackfin/include/asm/entry.h
> @@ -15,14 +15,6 @@
>  #define        LFLUSH_I_AND_D  0x00000808
>  #define        LSIGTRAP        5
>
> -/* process bits for task_struct.flags */
> -#define        PF_TRACESYS_OFF 3
> -#define        PF_TRACESYS_BIT 5
> -#define        PF_PTRACED_OFF  3
> -#define        PF_PTRACED_BIT  4
> -#define        PF_DTRACE_OFF   1
> -#define        PF_DTRACE_BIT   5
> -

looks like it has always been dead code on the Blackfin side having
originated from the m68k port.
Signed-off-by: Mike Frysinger <vapier@...too.org>

we can split the changeset to m68k & blackfin, or just let the m68k
guys run the thing through their tree.  i'm ok with it either way ...
i promise not to introduce conflicts into the blackfin file in the
mean time ;).
-mike
--
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