On 3/21/2024 5:44 AM, David Gow wrote:
> On Fri, 23 Feb 2024 at 22:07, Petr Tesarik
> wrote:
>>
>> From: Petr Tesarik
>>
>> If a segmentation fault is caused by accessing an address in the vmalloc
>> area, check that the target page is present.
>>
>> Currently, if the kernel hits a guard page in
On Fri, 23 Feb 2024 at 22:07, Petr Tesarik wrote:
>
> From: Petr Tesarik
>
> If a segmentation fault is caused by accessing an address in the vmalloc
> area, check that the target page is present.
>
> Currently, if the kernel hits a guard page in the vmalloc area, UML blindly
> assumes that the f
On 20/03/2024 14:09, Richard Weinberger wrote:
- Ursprüngliche Mail -
Von: "Petr Tesarik"
Yes. I'm just way behind my maintainer schedule. :-/
Understood. Thank you for your reply.
By the way, are you looking for more people to help with the amount of work?
Yes, help is always
- Ursprüngliche Mail -
> Von: "Petr Tesarik"
>> Yes. I'm just way behind my maintainer schedule. :-/
>
> Understood. Thank you for your reply.
>
> By the way, are you looking for more people to help with the amount of work?
Yes, help is always welcome!
Johannes and Anton do already a gr
t;> CC: "Roberto Sassu" , "petr"
>>
>> Gesendet: Montag, 18. März 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:
>>>
- Ursprüngliche Mail -
> Von: "Petr Tesarik"
> An: "richard" , "anton ivanov"
> , "Johannes Berg"
> , "linux-um" ,
> "linux-kernel"
> CC: "Roberto Sassu" , "petr"
> Gesendet: Montag,
On 3/12/2024 4:07 PM, Petr Tesarik wrote:
> On 2/23/2024 3:04 PM, Petr Tesarik wrote:
>> From: Petr Tesarik
>>
>> If a segmentation fault is caused by accessing an address in the vmalloc
>> area, check that the target page is present.
>>
>> Currently, if the kernel hits a guard page in the vmalloc
On 2/23/2024 3:04 PM, Petr Tesarik wrote:
> From: Petr Tesarik
>
> If a segmentation fault is caused by accessing an address in the vmalloc
> area, check that the target page is present.
>
> Currently, if the kernel hits a guard page in the vmalloc area, UML blindly
> assumes that the fault is c
From: Petr Tesarik
If a segmentation fault is caused by accessing an address in the vmalloc
area, check that the target page is present.
Currently, if the kernel hits a guard page in the vmalloc area, UML blindly
assumes that the fault is caused by a stale mapping and will be fixed by
flush_tlb_
