[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ca8891c9-c916-abf1-7370-5e4f37beaac9@huawei.com>
Date: Fri, 9 Feb 2018 16:28:06 +0200
From: Igor Stoppa <igor.stoppa@...wei.com>
To: Matthew Wilcox <willy@...radead.org>, Randy Dunlap <rdunlap@...radead.org>
CC: <jglisse@...hat.com>, <keescook@...omium.org>, <mhocko@...nel.org>,
<labbott@...hat.com>, <hch@...radead.org>, <cl@...ux.com>,
<linux-security-module@...r.kernel.org>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>, <kernel-hardening@...ts.openwall.com>
Subject: Re: [PATCH 1/6] genalloc: track beginning of allocations
On 05/02/18 05:45, Matthew Wilcox wrote:
> On Sun, Feb 04, 2018 at 02:34:08PM -0800, Randy Dunlap wrote:
>>> +/**
>>> + * cleart_bits_ll - according to the mask, clears the bits specified by
>>
>> clear_bits_ll
>
> 'make W=1' should catch this ... yes?
>
> (hint: building with 'make C=1 W=1' finds all kinds of interesting issues
> in your code. W=12 or W=123 finds too many false positives for my tastes)
ok, thank you, I will start using it
--
igor
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
