[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <nycvar.YFH.7.76.1901110836110.6626@cbobk.fhfr.pm>
Date: Fri, 11 Jan 2019 08:36:55 +0100 (CET)
From: Jiri Kosina <jikos@...nel.org>
To: Dave Chinner <david@...morbit.com>
cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Matthew Wilcox <willy@...radead.org>,
Jann Horn <jannh@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg KH <gregkh@...uxfoundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Michal Hocko <mhocko@...e.com>, Linux-MM <linux-mm@...ck.org>,
kernel list <linux-kernel@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>
Subject: Re: [PATCH] mm/mincore: allow for making sys_mincore() privileged
On Thu, 10 Jan 2019, Dave Chinner wrote:
> Sounds nice from a theoretical POV, but reality has taught us very
> different lessons.
>
> FWIW, a quick check of XFS's history so you understand how long this
> behaviour has been around. It was introduced in the linux port in 2001
> as direct IO support was being added:
>
> commit e837eac23662afae603aaaef7c94bc839c1b8f67
> Author: Steve Lord <lord@....com>
> Date: Mon Mar 5 16:47:52 2001 +0000
>
> Add bounds checking for direct I/O, do the cache invalidation for
> data coherency on direct I/O.
Out of curiosity, which repository is this from please? Even google
doesn't seem to know about this SHA.
Thanks,
--
Jiri Kosina
SUSE Labs
Powered by blists - more mailing lists