From: David Howells <dhowells@redhat.com>
To: Hillf Danton <hdanton@sina.com>
Cc: dhowells@redhat.com, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>,
David Hildenbrand <david@redhat.com>,
John Hubbard <jhubbard@nvidia.com>,
linux-mm@kvack.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Need help tracking down a bug in the bio-FOLL_PIN patches
Date: Tue, 07 Feb 2023 10:44:49 +0000 [thread overview]
Message-ID: <3024113.1675766689@warthog.procyon.org.uk> (raw)
In-Reply-To: <20230207094731.1390-1-hdanton@sina.com>
Hillf Danton <hdanton@sina.com> wrote:
> pipe_buf_release include/linux/pipe_fs_i.h:183 [inline]
> iov_iter_revert.part.0+0x402/0x730 lib/iov_iter.c:935
> iov_iter_revert+0x4c/0x60 lib/iov_iter.c:919
Yeah. That seems to be the problem.
Thanks,
David
prev parent reply other threads:[~2023-02-07 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 23:02 Need help tracking down a bug in the bio-FOLL_PIN patches David Howells
2023-02-06 23:20 ` David Howells
2023-02-07 9:47 ` Hillf Danton
2023-02-07 10:44 ` David Howells [this message]
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=3024113.1675766689@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=axboe@kernel.dk \
--cc=david@redhat.com \
--cc=hch@lst.de \
--cc=hdanton@sina.com \
--cc=jhubbard@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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