From: Greg KH <gregkh@linuxfoundation.org>
To: Yi Zhang <yi.zhang@redhat.com>
Cc: Sagi Grimberg <sagi@grimberg.me>, Hannes Reinecke <hare@suse.de>,
linux-nvme@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [bug report] nvme0n1 node still exists after blktests nvme-tcp/014 on 5.13.16-rc1
Date: Wed, 15 Sep 2021 15:00:40 +0200 [thread overview]
Message-ID: <YUHueINHsFDRwHPa@kroah.com> (raw)
In-Reply-To: <CAHj4cs8_382bLtbcR4F8RBJSmwMAdW22EiRycDjdLa0QtY2vnw@mail.gmail.com>
On Wed, Sep 15, 2021 at 08:41:21PM +0800, Yi Zhang wrote:
> On Tue, Sep 14, 2021 at 10:28 PM Sagi Grimberg <sagi@grimberg.me> wrote:
> >
> >
> > > Hello
> > > I found this failure on stable 5.13.16-rc1[1] and cannot reproduce it
> > > on 5.14, seems we are missing commit[2] on 5.13.y, could anyone help
> > > check it?
> >
> > Was it picked up and didn't apply correctly?
> >
>
> Hi Sagi
> I tried apply that patch to stable branch, but failed to do that,
> would you or Hannes mind help backport it, thanks.
>
> [linux-stable-rc ((daeb634aa75f...))]$ git am
> 0001-nvme-fix-refcounting-imbalance-when-all-paths-are-do.patch
> Applying: nvme: fix refcounting imbalance when all paths are down
> error: patch failed: drivers/nvme/host/nvme.h:716
> error: drivers/nvme/host/nvme.h: patch does not apply
> Patch failed at 0001 nvme: fix refcounting imbalance when all paths are down
> hint: Use 'git am --show-current-patch' to see the failed patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
>
> [linux-stable-rc ((daeb634aa75f...))]$ patch -p1 <
> 0001-nvme-fix-refcounting-imbalance-when-all-paths-are-do.patch
> patching file drivers/nvme/host/core.c
> Hunk #1 succeeded at 3761 (offset -46 lines).
> Hunk #2 succeeded at 3771 (offset -46 lines).
> Hunk #3 succeeded at 3790 (offset -46 lines).
> patching file drivers/nvme/host/multipath.c
> Hunk #1 succeeded at 757 (offset -3 lines).
> patching file drivers/nvme/host/nvme.h
> Hunk #1 FAILED at 716.
> Hunk #2 succeeded at 775 (offset 3 lines).
> 1 out of 2 hunks FAILED -- saving rejects to file drivers/nvme/host/nvme.h.rej
5.13 is only going to be around for a 2-3 more days, please move to
5.14.y at this point in time. No need to do any extra work for 5.13.y
at this point in time as it is about to be end-of-life.
thanks,
greg k-h
next prev parent reply other threads:[~2021-09-15 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 14:06 [bug report] nvme0n1 node still exists after blktests nvme-tcp/014 on 5.13.16-rc1 Yi Zhang
2021-09-14 14:28 ` Sagi Grimberg
2021-09-15 12:41 ` Yi Zhang
2021-09-15 13:00 ` Greg KH [this message]
2021-09-15 13:22 ` Yi Zhang
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=YUHueINHsFDRwHPa@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hare@suse.de \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=stable@vger.kernel.org \
--cc=yi.zhang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox