Re: Re: [PATCH v2] fix mmap return value when vma is merged after call_mmap()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: <akpm@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: Re: [PATCH v2] fix mmap return value when vma is merged after call_mmap()
From: Liu Zixian <liuzixian4@xxxxxxxxxx>
Date: Fri, 4 Dec 2020 10:29:50 +0800
Cc: <david@xxxxxxxxxx>, <hushiyuan@xxxxxxxxxx>, <jgg@xxxxxxxx>, <linmiaohe@xxxxxxxxxx>, <linux-mm@xxxxxxxxx>, <liuzixian4@xxxxxxxxxx>, <louhongxiang@xxxxxxxxxx>, <stable@xxxxxxxxxxxxxxx>
In-reply-to: <20201203142537.c69ab696573e63d54becff07@linux-foundation.org>
References: <20201203142537.c69ab696573e63d54becff07@linux-foundation.org>

> Has this bug actually been observed at runtime, or is it a theoretical
> from-code-inspection thing?

We have a driver which changes vm_flags, and this bug is found by our testcases.

Thanks to everyone for your review and email instructions, I will do better next time.

References:
- Re: [PATCH v2] fix mmap return value when vma is merged after call_mmap()
  - From: Andrew Morton

Prev by Date: Re: [linux-next:master] BUILD REGRESSION bfd521e1af519bb7096efc845f6a64a7de28c472
Next by Date: Re: [PATCH v2] mm: Don't fault around userfaultfd-registered regions on reads
Previous by thread: Re: [PATCH v2] fix mmap return value when vma is merged after call_mmap()
Next by thread: Re: [PATCH v2] fix mmap return value when vma is merged after call_mmap()
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux