From: Christoph Hellwig <hch@lst.de>
To: Marc Hartmayer <mhartmay@linux.ibm.com>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Block Mailing List <linux-block@vger.kernel.org>,
Linux SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: linux-next: possible bug in 'block: remove the BIO_NULL_MAPPED flag'
Date: Wed, 23 Sep 2020 16:54:11 +0200 [thread overview]
Message-ID: <20200923145411.GA15735@lst.de> (raw)
In-Reply-To: <87tuvo8xjo.fsf@linux.ibm.com>
I've reproduced this on x86 and am looking into the issue now.
prev parent reply other threads:[~2020-09-23 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 12:52 linux-next: possible bug in 'block: remove the BIO_NULL_MAPPED flag' Marc Hartmayer
2020-09-23 14:54 ` Christoph Hellwig [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=20200923145411.GA15735@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=borntraeger@de.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mhartmay@linux.ibm.com \
/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).