Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
In-Reply-To: <20221229170545.718264-1-ben-linux@fluff.org>
References: <20221229170545.718264-1-ben-linux@fluff.org>
Subject: Re: [PATCH] riscv: uaccess: fix type of 0 variable on error in get_user()
Message-Id: <167295914585.11542.3959390296046499334.b4-ty@rivosinc.com>
Date:   Thu, 05 Jan 2023 14:52:25 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Cc:     aou@eecs.berkeley.edu, Paul Walmsley <paul.walmsley@sifive.com>,
        linux-kernel@vger.kernel.org, Palmer Dabbelt <palmer@dabbelt.com>
From:   Palmer Dabbelt <palmer@rivosinc.com>
To:     linux-riscv@lists.infradead.org, Ben Dooks <ben-linux@fluff.org>
Precedence: bulk

On Thu, 29 Dec 2022 17:05:45 +0000, Ben Dooks wrote:
> If the get_user(x, ptr) has x as a pointer, then the setting
> of (x) = 0 is going to produce the following sparse warning,
> so fix this by forcing the type of 'x' when access_ok() fails.
> 
> fs/aio.c:2073:21: warning: Using plain integer as NULL pointer
> 
> 
> [...]

Applied, thanks!

[1/1] riscv: uaccess: fix type of 0 variable on error in get_user()
      https://git.kernel.org/palmer/c/b9b916aee671

Best regards,
-- 
Palmer Dabbelt <palmer@rivosinc.com>