Re: [PATCH] mm,madvise,hugetlb: check for 0-length range after end address adjustment

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

To: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [PATCH] mm,madvise,hugetlb: check for 0-length range after end address adjustment
From: Ricardo Cañuelo Navarro <rcn@xxxxxxxxxx>
Date: Mon, 03 Feb 2025 08:14:57 +0100
Cc: riel@xxxxxxxxxxx, linux-mm@xxxxxxxxx, stable@xxxxxxxxxxxxxxx, kernel-dev@xxxxxxxxxx, revest@xxxxxxxxxx
In-reply-to: <20250131142321.632a9468529d3267abe641af@linux-foundation.org>
References: <20250131143749.1435006-1-rcn@igalia.com> <20250131142321.632a9468529d3267abe641af@linux-foundation.org>

Hi Andrew,

On Fri, Jan 31 2025 at 14:23:21, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:

> Perhaps add a comment telling the user how this situation can come about?

Sure, I'll add the description to v2. Thanks for reviewing it!

Ricardo

References:
- [PATCH] mm,madvise,hugetlb: check for 0-length range after end address adjustment
  - From: Ricardo Cañuelo Navarro
- Re: [PATCH] mm,madvise,hugetlb: check for 0-length range after end address adjustment
  - From: Andrew Morton

Prev by Date: Re: [PATCHv4 01/17] zram: switch to non-atomic entry locking
Next by Date: Re: [PATCHv3 06/11] mm/vmscan: Use PG_dropbehind instead of PG_reclaim
Previous by thread: Re: [PATCH] mm,madvise,hugetlb: check for 0-length range after end address adjustment
Next by thread: [no subject]
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