From: Keith Busch <kbusch@kernel.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Sagi Grimberg <sagi@grimberg.me>, Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme: move nvme_stop_keep_alive() back to original position
Date: Tue, 21 Nov 2023 10:51:13 -0700 [thread overview]
Message-ID: <ZVzuEX4_nXf3B82h@kbusch-mbp> (raw)
In-Reply-To: <87313f89-cdd5-4511-87c3-816f545c4e60@suse.de>
On Tue, Nov 21, 2023 at 03:41:52PM +0100, Hannes Reinecke wrote:
> On 11/21/23 10:23, Sagi Grimberg wrote:
> >
> > > Stopping keep-alive not only stops the keep-alive workqueue,
> > > but also needs to be synchronized with I/O termination as we
> > > must not send a keep-alive command after all I/O had been
> > > terminated.
> > > So to avoid any regressions move the call to stop_keep_alive()
> > > back to its original position and ensure that keep-alive is
> > > correctly stopped failing to setup the admin queue.
> > >
> > > Fixes: 4733b65d82bd ("nvme: start keep-alive after admin queue setup")
> >
> > It should be folded in I guess. I suggest to either suggest an
> > alternative phrasing of the patch or resend an alternative patch
> > set.
> >
> Well, the original patch has already been merged to the nvme-6.7 tree,
> so I've attached the 'Fixes' tag.
> But let me know how you'd like to play it.
It's not just in nvme-6.7; it's merged upstream too. We can't squash it
now, so is it okay to apply this update as-is for the next pull request?
I'm going to send the next one out tomorrow before US holiday.
next prev parent reply other threads:[~2023-11-21 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 8:01 [PATCH] nvme: move nvme_stop_keep_alive() back to original position Hannes Reinecke
2023-11-21 9:23 ` Sagi Grimberg
2023-11-21 14:41 ` Hannes Reinecke
2023-11-21 17:51 ` Keith Busch [this message]
2023-11-22 8:16 ` Sagi Grimberg
2023-11-22 16:07 ` Keith Busch
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=ZVzuEX4_nXf3B82h@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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