linux-kernel - Re: [PATCH -next] x86/mm: fix an unused variable "tsk" warning

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]

Message-ID: <20190612195339.GR32652@zn.tnic>
Date:   Wed, 12 Jun 2019 21:53:39 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     "Eric W. Biederman" <ebiederm@...ssion.com>
Cc:     Qian Cai <cai@....pw>, mingo@...hat.com, tglx@...utronix.de,
        dave.hansen@...ux.intel.com, luto@...nel.org, peterz@...radead.org,
        hpa@...or.com, x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next] x86/mm: fix an unused variable "tsk" warning

On Wed, Jun 12, 2019 at 01:19:06PM -0500, Eric W. Biederman wrote:
> Since I am removing the tsk parameter from all of the synchrnous signal
> sending functions, on all of the architectures it was easier to go
> through my own tree than -tip.

Yeah, I remember reading a mail about it...

> The removal of tsk from force_sig_fault is what caused the warning
> in do_sigbus.
> 
> My apologies I was a little slow in getting that patch added and
> generating work for other folks.

That's fine - now we know what the situation is.

Thx.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.