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: <20180301171609.c1968b89a15320186122e34e@linux-foundation.org>
Date:   Thu, 1 Mar 2018 17:16:09 -0800
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Mark Rutland <mark.rutland@....com>
Cc:     linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
        Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
        Michal Hocko <mhocko@...e.com>,
        Peter Zijlstra <peterz@...raded.org>,
        Rik van Riel <riel@...hat.com>,
        Will Deacon <will.deacon@....com>
Subject: Re: [PATCH] Detect early free of a live mm

On Wed, 28 Feb 2018 12:14:58 +0000 Mark Rutland <mark.rutland@....com> wrote:

> KASAN splats indicate that in some cases we free a live mm, then
> continue to access it, with potentially disastrous results. This is
> likely due to a mismatched mmdrop() somewhere in the kernel, but so far
> the culprit remains elusive.
> 
> Let's have __mmdrop() verify that the mm isn't live for the current
> task, similar to the existing check for init_mm. This way, we can catch
> this class of issue earlier, and without requiring KASAN.

Presumably the results usually aren't disastrous.  But they will be if
we go and add BUG_ON()s!  Can we make this WARN_ON[_ONCE]()?  We should
still get the same info from testers.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ