From: Jason Gunthorpe <jgg@ziepe.ca>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Christopher Lameter <cl@linux.com>,
linux-rdma <linux-rdma@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>, Michal Hocko <mhocko@kernel.org>
Subject: Re: [LSFMM] RDMA data corruption potential during FS writeback
Date: Fri, 18 May 2018 21:24:00 -0600 [thread overview]
Message-ID: <20180519032400.GA12517@ziepe.ca> (raw)
In-Reply-To: <c8861cbb-5b2e-d6e2-9c89-66c5c92181e6@nvidia.com>
On Fri, May 18, 2018 at 07:33:41PM -0700, John Hubbard wrote:
> On 05/18/2018 01:23 PM, Dan Williams wrote:
> > On Fri, May 18, 2018 at 10:36 AM, Jason Gunthorpe <jgg@ziepe.ca> wrote:
> >> On Fri, May 18, 2018 at 04:47:48PM +0000, Christopher Lameter wrote:
> >>> On Fri, 18 May 2018, Jason Gunthorpe wrote:
> >>>
> >>>
> >>> The newcomer here is RDMA. The FS side is the mainstream use case and has
> >>> been there since Unix learned to do paging.
> >>
> >> Well, it has been this way for 12 years, so it isn't that new.
> >>
> >> Honestly it sounds like get_user_pages is just a broken Linux
> >> API??
> >>
> >> Nothing can use it to write to pages because the FS could explode -
> >> RDMA makes it particularly easy to trigger this due to the longer time
> >> windows, but presumably any get_user_pages could generate a race and
> >> hit this? Is that right?
>
> +1, and I am now super-interested in this conversation, because
> after tracking down a kernel BUG to this classic mistaken pattern:
>
> get_user_pages (on file-backed memory from ext4)
> ...do some DMA
> set_pages_dirty
> put_page(s)
Ummm, RDMA has done essentially that since 2005, since when did it
become wrong? Do you have some references? Is there some alternative?
See __ib_umem_release
> ...there is (rarely!) a backtrace from ext4, that disavows ownership of
> any such pages.
Yes, I've seen that oops with RDMA, apparently isn't actually that
rare if you tweak things just right.
I thought it was an obscure ext4 bug :(
> Because the obvious "fix" in device driver land is to use a dedicated
> buffer for DMA, and copy to the filesystem buffer, and of course I will
> get *killed* if I propose such a performance-killing approach. But a
> core kernel fix really is starting to sound attractive.
Yeah, killed is right. That idea totally cripples RDMA.
What is the point of get_user_pages FOLL_WRITE if you can't write to
and dirty the pages!?!
Jason
next prev parent reply other threads:[~2018-05-19 3:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 14:37 [LSFMM] RDMA data corruption potential during FS writeback Christopher Lameter
2018-05-18 15:49 ` Jason Gunthorpe
2018-05-18 16:47 ` Christopher Lameter
2018-05-18 17:36 ` Jason Gunthorpe
2018-05-18 20:23 ` Dan Williams
2018-05-19 2:33 ` John Hubbard
2018-05-19 3:24 ` Jason Gunthorpe [this message]
2018-05-19 3:51 ` Dan Williams
2018-05-19 5:38 ` John Hubbard
2018-05-21 14:38 ` Matthew Wilcox
2018-05-23 23:03 ` John Hubbard
2018-05-21 13:37 ` Christopher Lameter
2018-05-21 13:59 ` Christopher Lameter
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=20180519032400.GA12517@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=cl@linux.com \
--cc=dan.j.williams@intel.com \
--cc=jhubbard@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mhocko@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).