From: Christoph Hellwig <hch@lst.de>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
dm-devel@redhat.com, linux-block@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v3 0/4] nvme: improve error handling and ana_state to work well with dm-multipath
Date: Tue, 20 Apr 2021 11:37:20 +0200 [thread overview]
Message-ID: <20210420093720.GA28874@lst.de> (raw)
In-Reply-To: <20210416235329.49234-1-snitzer@redhat.com>
> RHEL9 is coming, would really prefer that these changes land upstream
> rather than carry them within RHEL.
We've told from the very beginning that dm-multipth on nvme is not
a support configuration. Red Hat decided to ignore that and live with the
pain. Your major version change is a chance to fix this up on the Red Hat
side, not to resubmit bogus patches upstream.
In other words: please get your house in order NOW.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
dm-devel@redhat.com, linux-block@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v3 0/4] nvme: improve error handling and ana_state to work well with dm-multipath
Date: Tue, 20 Apr 2021 11:37:20 +0200 [thread overview]
Message-ID: <20210420093720.GA28874@lst.de> (raw)
In-Reply-To: <20210416235329.49234-1-snitzer@redhat.com>
> RHEL9 is coming, would really prefer that these changes land upstream
> rather than carry them within RHEL.
We've told from the very beginning that dm-multipth on nvme is not
a support configuration. Red Hat decided to ignore that and live with the
pain. Your major version change is a chance to fix this up on the Red Hat
side, not to resubmit bogus patches upstream.
In other words: please get your house in order NOW.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org
Subject: Re: [dm-devel] [PATCH v3 0/4] nvme: improve error handling and ana_state to work well with dm-multipath
Date: Tue, 20 Apr 2021 11:37:20 +0200 [thread overview]
Message-ID: <20210420093720.GA28874@lst.de> (raw)
In-Reply-To: <20210416235329.49234-1-snitzer@redhat.com>
> RHEL9 is coming, would really prefer that these changes land upstream
> rather than carry them within RHEL.
We've told from the very beginning that dm-multipth on nvme is not
a support configuration. Red Hat decided to ignore that and live with the
pain. Your major version change is a chance to fix this up on the Red Hat
side, not to resubmit bogus patches upstream.
In other words: please get your house in order NOW.
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2021-04-20 9:37 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 23:53 [PATCH v3 0/4] nvme: improve error handling and ana_state to work well with dm-multipath Mike Snitzer
2021-04-16 23:53 ` [dm-devel] " Mike Snitzer
2021-04-16 23:53 ` Mike Snitzer
2021-04-16 23:53 ` [PATCH v4 1/3] nvme: return BLK_STS_DO_NOT_RETRY if the DNR bit is set Mike Snitzer
2021-04-16 23:53 ` [dm-devel] " Mike Snitzer
2021-04-16 23:53 ` Mike Snitzer
2021-04-20 9:34 ` Christoph Hellwig
2021-04-20 9:34 ` [dm-devel] " Christoph Hellwig
2021-04-20 9:34 ` Christoph Hellwig
2021-04-16 23:53 ` [PATCH v4 2/3] nvme: allow local retry and proper failover for REQ_FAILFAST_TRANSPORT Mike Snitzer
2021-04-16 23:53 ` [dm-devel] " Mike Snitzer
2021-04-16 23:53 ` Mike Snitzer
2021-04-16 23:53 ` [PATCH v4 3/3] nvme: decouple basic ANA log page re-read support from native multipathing Mike Snitzer
2021-04-16 23:53 ` [dm-devel] " Mike Snitzer
2021-04-16 23:53 ` Mike Snitzer
2021-04-20 9:34 ` Christoph Hellwig
2021-04-20 9:34 ` [dm-devel] " Christoph Hellwig
2021-04-20 9:34 ` Christoph Hellwig
2021-04-20 14:17 ` Mike Snitzer
2021-04-20 14:17 ` [dm-devel] " Mike Snitzer
2021-04-20 14:17 ` Mike Snitzer
2021-04-17 0:02 ` [PATCH v4 0/4] nvme: improve error handling and ana_state to work well with dm-multipath Mike Snitzer
2021-04-17 0:02 ` [dm-devel] " Mike Snitzer
2021-04-17 0:02 ` Mike Snitzer
2021-04-19 14:56 ` Mike Snitzer
2021-04-19 14:56 ` [dm-devel] " Mike Snitzer
2021-04-19 14:56 ` Mike Snitzer
2021-04-20 9:37 ` Christoph Hellwig [this message]
2021-04-20 9:37 ` [dm-devel] [PATCH v3 " Christoph Hellwig
2021-04-20 9:37 ` Christoph Hellwig
2021-04-20 14:38 ` Mike Snitzer
2021-04-20 14:38 ` [dm-devel] " Mike Snitzer
2021-04-20 14:38 ` Mike Snitzer
2021-04-20 15:46 ` Laurence Oberman
2021-04-20 15:46 ` [dm-devel] " Laurence Oberman
2021-04-20 15:46 ` Laurence Oberman
2021-05-01 11:58 ` Hannes Reinecke
2021-05-01 11:58 ` [dm-devel] " Hannes Reinecke
2021-05-01 11:58 ` Hannes Reinecke
2021-05-01 15:19 ` Mike Snitzer
2021-05-01 15:19 ` [dm-devel] " Mike Snitzer
2021-05-01 15:19 ` Mike Snitzer
-- strict thread matches above, loose matches on Subject: below --
2021-04-16 22:06 Mike Snitzer
2021-04-16 22:06 ` Mike Snitzer
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=20210420093720.GA28874@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=snitzer@redhat.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 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.