linux-kernel - Re: [PATCH v3 05/15] h8300: Process and signal

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: <CAFLxGvxeT3uydJVXfyDX4VnsThVJ5r40osnGE1J5btLvvz9JnQ@mail.gmail.com>
Date:	Sun, 15 Feb 2015 20:38:25 +0100
From:	Richard Weinberger <richard.weinberger@...il.com>
To:	Yoshinori Sato <ysato@...rs.sourceforge.jp>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linux-Arch <linux-arch@...r.kernel.org>
Subject: Re: [PATCH v3 05/15] h8300: Process and signal

On Sun, Feb 15, 2015 at 8:49 AM, Yoshinori Sato
<ysato@...rs.sourceforge.jp> wrote:
> +       usig = current_thread_info()->exec_domain
> +               && current_thread_info()->exec_domain->signal_invmap
> +               && sig < 32
> +               ? current_thread_info()->exec_domain->signal_invmap[sig]
> +               : sig;

Does h8300 really need signal mapping?
I'm very sure you can drop this.
In fact I'm working in patch set to rip it out tree wide as we have
only a single (broken)
in-tree user.

-- 
Thanks,
//richard
--
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/