[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210121144627.64a60437fe97786596f389d0@linux-foundation.org>
Date: Thu, 21 Jan 2021 14:46:27 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Jarkko Sakkinen <jarkko@...nel.org>
Cc: Tianjia Zhang <tianjia.zhang@...ux.alibaba.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>, Shuah Khan <shuah@...nel.org>,
haitao.huang@...el.com, Kai Huang <kai.huang@...el.com>,
x86@...nel.org, linux-sgx@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-kselftest@...r.kernel.org,
Jia Zhang <zhang.jia@...ux.alibaba.com>
Subject: Re: [PATCH] mm: Optimizing error condition detection in
do_mprotect_pkey()
On Wed, 20 Jan 2021 16:29:20 +0200 Jarkko Sakkinen <jarkko@...nel.org> wrote:
>
>
> On Mon, Jan 18, 2021 at 09:33:10PM +0800, Tianjia Zhang wrote:
> > Obviously, the error variable detection of the if statement is
> > for the mprotect callback function, so it is also put into the
> > scope of calling callbck.
> >
> > Reported-by: Jia Zhang <zhang.jia@...ux.alibaba.com>
> > Signed-off-by: Tianjia Zhang <tianjia.zhang@...ux.alibaba.com>
>
> No fixes tag, no description what this commit does. Nothing
> makes sense to me.
It's a little cleanup. Makes the flow at this site consistent with the
other places where this function handles errors. I added a bit to the
changelog mentioning this.
Powered by blists - more mailing lists