[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160107151356.0e131b25f5740f6046221419@linux-foundation.org>
Date: Thu, 7 Jan 2016 15:13:56 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Mike Kravetz <mike.kravetz@...cle.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Hillf Danton <hillf.zj@...baba-inc.com>,
Hugh Dickins <hughd@...gle.com>,
Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
Davidlohr Bueso <dave@...olabs.net>,
Dave Hansen <dave.hansen@...ux.intel.com>,
stable@...r.kernel.org
Subject: Re: [PATCH] mm/hugetlbfs Fix bugs in hugetlb_vmtruncate_list
On Thu, 7 Jan 2016 14:35:37 -0800 Mike Kravetz <mike.kravetz@...cle.com> wrote:
> Hillf Danton noticed bugs in the hugetlb_vmtruncate_list routine.
> The argument end is of type pgoff_t. It was being converted to a
> vaddr offset and passed to unmap_hugepage_range. However, end
> was also being used as an argument to the vma_interval_tree_foreach
> controlling loop. In addition, the conversion of end to vaddr offset
> was incorrect.
Could we please have a description of the user-visible effects of the
bug? It's always needed for -stable things. And for all bugfixes, really.
(stable@...r.kernel.org[4.3] isn't an email address btw - my client barfed)
Powered by blists - more mailing lists