Received-SPF: pass (google.com: domain of linux-kernel+bounces-107669-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
From: Roman Smirnov <r.smirnov@omp.ru>
To: Jarkko Sakkinen <jarkko@kernel.org>, David Howells <dhowells@redhat.com>,
	Herbert Xu <herbert@gondor.apana.org.au>, "David S. Miller"
	<davem@davemloft.net>, Andrew Zaborowski <andrew.zaborowski@intel.com>
CC: "keyrings@vger.kernel.org" <keyrings@vger.kernel.org>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>, "Sergey
 Shtylyov" <s.shtylyov@omp.ru>
Subject: Re: [PATCH] KEYS: prevent NULL pointer dereference in
 find_asymmetric_key()
Thread-Topic: [PATCH] KEYS: prevent NULL pointer dereference in
 find_asymmetric_key()
Thread-Index: AQHadsRHcr0dJekxEkCC6oTcOjjyP7E9+xQAgAEukF0=
Date: Tue, 19 Mar 2024 14:44:35 +0000
Message-ID: <b5f21d1175c142efb52e68a24bc4165a@omp.ru>
References: <20240315103320.18754-1-r.smirnov@omp.ru>,<CZX9T3TU6YU0.3JE9M7M3ENUE0@kernel.org>
In-Reply-To: <CZX9T3TU6YU0.3JE9M7M3ENUE0@kernel.org>
Accept-Language: ru-RU, en-US
Content-Language: ru-RU
x-kse-attachment-filter-triggered-filters: Clean
x-kse-bulkmessagesfiltering-scan-result: InTheLimit
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
X-Mailing-List: linux-kernel@vger.kernel.org
List-Id: <linux-kernel.vger.kernel.org>
List-Subscribe: <mailto:linux-kernel+subscribe@vger.kernel.org>
List-Unsubscribe: <mailto:linux-kernel+unsubscribe@vger.kernel.org>
MIME-Version: 1.0

On Tue, 19 Mar 2024 01:39:00 +0200 Jarkko Sakkinen wrote:
> On Fri Mar 15, 2024 at 12:33 PM EET, Roman Smirnov wrote:
> > With the current code, in case all NULLs are passed in id_{0,1,2},
>=20
> "current code" is not unambigious reference of any part of the kernel
> tree. Please just write down the function name instead.
>=20
> > the kernel will first print out a WARNING and then have an oops
> > because id_2 gets dereferenced anyway.
>=20
> Would be more exact":
>=20
> s/print out a WARNING/emit WARN/

Okay, I'll prepare a second version of the patch.

> > Note that WARN_ON() is also considered harmful by Greg Kroah-
> > Hartman since it causes the Android kernels to panic as they
> > get booted with the panic_on_warn option.
>=20
> Despite full respect to Greg, and agreeing what he had said about
> the topic (which you are lacking lore link meaning that in all
> cases the current description is incomplete), the only thing that
> should be documented should be that since WARN_ON() can emit
> panic when panic_on_warn is set in the *kernel command-line*
> (not "option") this condition should be relaxed.

Here's a link to the discussion:
https://lore.kernel.org/all/2024011213-situated-augmented-64a4@gregkh/
From the context, I thought WARN_ON() would be better removed.

> >
> > Found by Linux Verification Center (linuxtesting.org) with Svace.
>=20
> I'm not sure if this should be part of the commit message.

I have already submitted patches with this line, some have been
accepted. It is important for the Linux Verification Center to mark
patches as closing issues found with Svace.

> >
> > Fixes: 7d30198ee24f ("keys: X.509 public key issuer lookup without AKID=
")
> > Suggested-by: Sergey Shtylyov <s.shtylyov@omp.ru>
>=20
> Should be reported-by.

The suggested-by tag belongs to Sergey because he suggested the fix,
subject/description of the patch. The tag reported-by belongs to
Svace tool.

Thank you for the reply.=