Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 1D7D8C433F2
Subject:  Query : Regarding csdb barrier with llvm compiler
From:   Gaurav Kohli <gkohli@codeaurora.org>
To:     Robin Murphy <robin.murphy@arm.com>,
        Will Deacon <will.deacon@arm.com>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Mark Rutland <mark.rutland@arm.com>,
        linux-kernel <linux-kernel@vger.kernel.org>
Cc:     linux-arm-msm@vger.kernel.org, jannh@google.com
References: <6ffd3fc0-4d9f-364b-4ab0-b90147689334@codeaurora.org>
Message-ID: <77aec890-d514-8e13-2322-55e61f587236@codeaurora.org>
Date:   Tue, 31 Mar 2020 14:55:08 +0530
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <6ffd3fc0-4d9f-364b-4ab0-b90147689334@codeaurora.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

<Resending again, saw some failure messages on previous mail>

Hi ,

Right now we are using array_index_nospec api in linux kernel and using 
in the place where we think speculative out of bound access may happen.

This thing is applicable with GCC tool chain, as for GCC we have to use 
builtin api to place csdb in the required places.

Recently llvm toolchain comes with hardening option which will place 
csdb in the required places, Do we have any plan to use this thing in 
linux kernel.

Regards
Gaurav

-- 
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center,
Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.