Hey Mike,
The point is: blk_path_error() has nothing to do with NVMe errors.
This is dm-multipath logic stuck in the middle of the NVMe error
handling code.
No, it is a means to have multiple subsystems (to this point both SCSI
and NVMe) doing the correct thing when translating subsystem sp
The pull request you sent on Fri, 7 Aug 2020 12:03:27 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git
> tags/for-5.9/dm-changes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2f12d44085dabf5fa5779ff0bb0aaa1b2cc768cb
Thank you!
--
D
On Fri, Aug 07 2020 at 4:11pm -0400,
Linus Torvalds wrote:
> On Fri, Aug 7, 2020 at 9:03 AM Mike Snitzer wrote:
> >
> > - DM crypt improvement to optionally avoid async processing via
> > workqueues for reads and/or writes -- via "no_read_workqueue" and
> > "no_write_workqueue" features. T
On Fri, Aug 7, 2020 at 9:03 AM Mike Snitzer wrote:
>
> - DM crypt improvement to optionally avoid async processing via
> workqueues for reads and/or writes -- via "no_read_workqueue" and
> "no_write_workqueue" features. This more direct IO processing
> improves latency and throughput with f
On Thu, 6 Aug 2020, Mimi Zohar wrote:
> On Thu, 2020-08-06 at 09:51 +1000, James Morris wrote:
> > On Wed, 5 Aug 2020, Mimi Zohar wrote:
> >
> > > If block layer integrity was enough, there wouldn't have been a need
> > > for fs-verity. Even fs-verity is limited to read only filesystems,
> > >
On Fri, Aug 07 2020 at 12:03pm -0400,
Mike Snitzer wrote:
> Hi Linus,
>
> The following changes since commit 11ba468877bb23f28956a35e896356252d63c983:
>
> Linux 5.8-rc5 (2020-07-12 16:34:50 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/gi
Hi Linus,
The following changes since commit 11ba468877bb23f28956a35e896356252d63c983:
Linux 5.8-rc5 (2020-07-12 16:34:50 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git
tags/for-5.9/dm-changes
for you to fetch change
On Thu, 2020-08-06 at 09:51 +1000, James Morris wrote:
> On Wed, 5 Aug 2020, Mimi Zohar wrote:
>
> > If block layer integrity was enough, there wouldn't have been a need
> > for fs-verity. Even fs-verity is limited to read only filesystems,
> > which makes validating file integrity so much easie
