[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2236FBA76BA1254E88B949DDB74E612B41C13F55@IRSMSX102.ger.corp.intel.com>
Date: Thu, 17 Nov 2016 09:04:44 +0000
From: "Reshetova, Elena" <elena.reshetova@...el.com>
To: Peter Zijlstra <peterz@...radead.org>
CC: Rik van Riel <riel@...hat.com>, "kernel-hardening@...ts.openwall.com"
<kernel-hardening@...ts.openwall.com>, Will Deacon <will.deacon@....com>,
Greg KH <gregkh@...uxfoundation.org>, David Windsor <dave@...gbits.org>,
"Arnd Bergmann" <arnd@...db.de>, Thomas Gleixner <tglx@...utronix.de>, Ingo
Molnar <mingo@...hat.com>, "Anvin, H Peter" <h.peter.anvin@...el.com>,
"Julia.Lawall@...6.fr" <Julia.Lawall@...6.fr>
Subject: RE: Re: [RFC v4 PATCH 00/13] HARDENED_ATOMIC
> I have a coccinelle rule now that found about 15 usages of it.
>Right, so can coccinelle detect the call_rcu/free call that is conditional on the dec_and_test when its hidden inside a few function calls?
Yes, it can. However, I haven't expanded the rule yet to cover cases when "hidden inside a few function calls" goes outside of one .c or .h file. Coccinelle supports that, but I have to experiment fist if it doesn't bring more false positives that current setup.
>Also, we should really have a "make spatch" target so that we can run the thing concurrently with -j80 or somesuch, because as is coccinelle is unbearably slow.
The currents rules are very simple, the full run on the whole tree even without any pre-indexing, multithreading and etc. takes around 1 min only.
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.
