[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170206085133.GB4004@quack2.suse.cz>
Date: Mon, 6 Feb 2017 09:51:33 +0100
From: Jan Kara <jack@...e.cz>
To: Dave Jiang <dave.jiang@...el.com>
Cc: akpm@...ux-foundation.org, mawilcox@...rosoft.com,
linux-nvdimm@...ts.01.org, dave.hansen@...ux.intel.com,
linux-xfs@...r.kernel.org, linux-mm@...ck.org,
kirill.shutemov@...ux.intel.com, jack@...e.com,
dan.j.williams@...el.com, linux-ext4@...r.kernel.org,
ross.zwisler@...ux.intel.com, vbabka@...e.cz
Subject: Re: [PATCH] mm: replace FAULT_FLAG_SIZE with parameter to huge_fault
On Fri 03-02-17 14:31:22, Dave Jiang wrote:
> Since the introduction of FAULT_FLAG_SIZE to the vm_fault flag, it has
> been somewhat painful with getting the flags set and removed at the
> correct locations. More than one kernel oops was introduced due to
> difficulties of getting the placement correctly. Removing the flag
> values and introducing an input parameter to huge_fault that indicates
> the size of the page entry. This makes the code easier to trace and
> should avoid the issues we see with the fault flags where removal of the
> flag was necessary in the fallback paths.
>
> Signed-off-by: Dave Jiang <dave.jiang@...el.com>
Yeah, the code looks less error-prone this way. I like it. You can add:
Reviewed-by: Jan Kara <jack@...e.cz>
Honza
--
Jan Kara <jack@...e.com>
SUSE Labs, CR
Powered by blists - more mailing lists