Received-SPF: pass (google.com: domain of linux-kernel+bounces-108189-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Date: Tue, 19 Mar 2024 23:18:05 +0100 (CET)
From: Richard Weinberger <richard@nod.at>
To: Petr Tesarik <petrtesarik@huaweicloud.com>
Cc: anton ivanov <anton.ivanov@cambridgegreys.com>, 
	Johannes Berg <johannes@sipsolutions.net>, 
	linux-um <linux-um@lists.infradead.org>, 
	linux-kernel <linux-kernel@vger.kernel.org>, 
	Roberto Sassu <roberto.sassu@huaweicloud.com>, 
	petr <petr@tesarici.cz>
Message-ID: <1418379493.78340.1710886685735.JavaMail.zimbra@nod.at>
In-Reply-To: <8d45f94c-bce1-4327-9573-cec254a4e9c3@huaweicloud.com>
References: <20240223140435.1240-1-petrtesarik@huaweicloud.com> <9284cda7-d7e3-4390-bf62-58092e97d1c8@huaweicloud.com> <8d45f94c-bce1-4327-9573-cec254a4e9c3@huaweicloud.com>
Subject: Re: [PATCH RESEND 1/1] um: oops on accessing a non-present page in
 the vmalloc area
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Thread-Topic: oops on accessing a non-present page in the vmalloc area
Thread-Index: OdzHbbhSrpqdStaC7MekET1pCSEHow==

----- Urspr=C3=BCngliche Mail -----
> Von: "Petr Tesarik" <petrtesarik@huaweicloud.com>
> An: "richard" <richard@nod.at>, "anton ivanov" <anton.ivanov@cambridgegre=
ys.com>, "Johannes Berg"
> <johannes@sipsolutions.net>, "linux-um" <linux-um@lists.infradead.org>, "=
linux-kernel" <linux-kernel@vger.kernel.org>
> CC: "Roberto Sassu" <roberto.sassu@huaweicloud.com>, "petr" <petr@tesaric=
i.cz>
> Gesendet: Montag, 18. M=C3=A4rz 2024 14:09:07
> Betreff: Re: [PATCH RESEND 1/1] um: oops on accessing a non-present page =
in the vmalloc area

> On 3/12/2024 4:07 PM, Petr Tesarik wrote:
>> On 2/23/2024 3:04 PM, Petr Tesarik wrote:
>>> From: Petr Tesarik <petr.tesarik1@huawei-partners.com>
>>>
>>> If a segmentation fault is caused by accessing an address in the vmallo=
c
>>> area, check that the target page is present.
>>>
>>> Currently, if the kernel hits a guard page in the vmalloc area, UML bli=
ndly
>>> assumes that the fault is caused by a stale mapping and will be fixed b=
y
>>> flush_tlb_kernel_vm(). Unsurprisingly, if the fault is caused by access=
ing
>>> a guard page, no mapping is created, and when the faulting instruction =
is
>>> restarted, it will cause exactly the same fault again, effectively crea=
ting
>>> an infinite loop.
>>=20
>> Ping. Any comment on this fix?
>=20
> I don't think I have seen a reply from you. If you did comment, then
> your email has not reached me.
>=20
> Please, can you confirm you have seen my patch?

Yes. I'm just way behind my maintainer schedule. :-/

Thanks,
//richard