From: Christoph Hellwig <hch@lst.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
john.hubbard@gmail.com, Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@kernel.org>,
Christopher Lameter <cl@linux.com>, Jan Kara <jack@suse.cz>,
Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-rdma <linux-rdma@vger.kernel.org>,
John Hubbard <jhubbard@nvidia.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 2/2] mm: set PG_dma_pinned on get_user_pages*()
Date: Mon, 18 Jun 2018 10:11:13 +0200 [thread overview]
Message-ID: <20180618081113.GA16991@lst.de> (raw)
In-Reply-To: <CAPcyv4gayKk_zHDYAvntware12qMXWjnnL_FDJNUQsJS_zNfDw@mail.gmail.com>
On Sun, Jun 17, 2018 at 01:10:04PM -0700, Dan Williams wrote:
> I believe kernel behavior regression is a primary concern as now
> fallocate() and truncate() can randomly fail where they didn't before.
Fail or block forever due to actions of other unprivileged users.
That is a complete no-go.
next prev parent reply other threads:[~2018-06-18 8:11 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 1:25 [PATCH 0/2] mm: gup: don't unmap or drop filesystem buffers john.hubbard
2018-06-17 1:25 ` [PATCH 1/2] consolidate get_user_pages error handling john.hubbard
2018-06-17 1:25 ` [PATCH 2/2] mm: set PG_dma_pinned on get_user_pages*() john.hubbard
2018-06-17 19:53 ` Dan Williams
2018-06-17 20:04 ` Jason Gunthorpe
2018-06-17 20:10 ` Dan Williams
2018-06-17 20:28 ` John Hubbard
2018-06-17 20:28 ` John Hubbard
2018-06-18 8:12 ` Christoph Hellwig
2018-06-18 17:50 ` John Hubbard
2018-06-18 17:50 ` John Hubbard
2018-06-18 17:56 ` Dan Williams
2018-06-18 18:14 ` John Hubbard
2018-06-18 18:14 ` John Hubbard
2018-06-18 19:21 ` Dan Williams
2018-06-18 19:31 ` Jason Gunthorpe
2018-06-18 20:04 ` Dan Williams
2018-06-18 21:36 ` John Hubbard
2018-06-19 8:29 ` Jan Kara
2018-06-19 9:02 ` Matthew Wilcox
2018-06-19 10:41 ` Jan Kara
2018-06-19 18:11 ` John Hubbard
2018-06-20 1:24 ` Dan Williams
2018-06-20 1:34 ` John Hubbard
2018-06-20 1:57 ` Dan Williams
2018-06-20 2:03 ` John Hubbard
2018-06-20 12:08 ` Jan Kara
2018-06-20 22:55 ` John Hubbard
2018-06-21 16:30 ` Jan Kara
2018-06-25 15:21 ` Jan Kara
2018-06-25 19:03 ` John Hubbard
2018-06-26 7:52 ` Jan Kara
2018-06-26 6:31 ` John Hubbard
2018-06-26 11:48 ` Jan Kara
2018-06-26 13:47 ` Michal Hocko
2018-06-26 16:48 ` Jan Kara
2018-06-27 11:32 ` Michal Hocko
2018-06-27 11:53 ` Jan Kara
2018-06-27 11:59 ` Michal Hocko
2018-06-27 12:42 ` Jan Kara
2018-06-27 14:57 ` Jason Gunthorpe
2018-06-27 17:02 ` Jan Kara
2018-06-28 2:42 ` John Hubbard
2018-06-28 9:17 ` Jan Kara
2018-07-02 5:52 ` Leon Romanovsky
2018-07-02 6:10 ` John Hubbard
2018-07-02 6:34 ` Leon Romanovsky
2018-07-02 6:41 ` John Hubbard
2018-07-02 10:36 ` Michal Hocko
2018-07-02 7:02 ` Jan Kara
2018-07-02 14:48 ` Michal Hocko
2018-07-02 6:58 ` Jan Kara
2018-06-18 8:11 ` Christoph Hellwig [this message]
2018-06-19 6:15 ` Leon Romanovsky
2018-06-17 22:19 ` John Hubbard
2018-06-17 22:19 ` John Hubbard
2018-06-18 7:56 ` Christoph Hellwig
2018-06-18 17:44 ` John Hubbard
2018-06-18 17:44 ` John Hubbard
2018-06-17 21:54 ` [PATCH 0/2] mm: gup: don't unmap or drop filesystem buffers Christopher Lameter
2018-06-17 22:23 ` John Hubbard
2018-06-17 22:23 ` John Hubbard
2018-06-18 8:10 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180618081113.GA16991@lst.de \
--to=hch@lst.de \
--cc=cl@linux.com \
--cc=dan.j.williams@intel.com \
--cc=jack@suse.cz \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=john.hubbard@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.