From: kbusch@kernel.org (Keith Busch)
Subject: A kernel warning when entering suspend
Date: Mon, 8 Apr 2019 09:07:51 -0600 [thread overview]
Message-ID: <20190408150750.GB32498@localhost.localdomain> (raw)
In-Reply-To: <AM6PR06MB50635FC76FFD74DA6C423182A1520@AM6PR06MB5063.eurprd06.prod.outlook.com>
On Sat, Apr 06, 2019@09:12:12AM -0700, fin4478 fin4478 wrote:
> On Sat, 6 Apr 2019 23:31:51 +0800
> Dongli Zhang <dongli.zhang@oracle.com> wrote:
>
>
> > I am not able to reproduce anymore with below patch:
> >
> > diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> > index a90cf5d..90f6e80 100644
> > --- a/drivers/nvme/host/pci.c
> > +++ b/drivers/nvme/host/pci.c
> > @@ -1083,6 +1083,9 @@ static int nvme_poll_irqdisable(struct
> > nvme_queue *nvmeq, unsigned int tag)
> > u16 start, end;
> > int found;
> >
> > + if (!nvme_cqe_pending(nvmeq))
> > + return 0;
> > +
> > /*
> > * For a poll queue we need to protect against the polling
> > thread
> > * using the CQ lock. For normal interrupt driven threads we
> > have
> >
> > Dongli Zhang
>
> Confirming. This bug is fixed with this patch.
I think the patch makes sense, though you'd still have a problem if
there is a cqe pending when you reach this point.
prev parent reply other threads:[~2019-04-08 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 8:23 A kernel warning when entering suspend fin4478 fin4478
2019-04-04 8:55 ` Ming Lei
2019-04-04 11:14 ` Thomas Gleixner
2019-12-23 14:52 ` Maxim Levitsky
2020-01-16 13:58 ` Maxim Levitsky
2019-04-04 15:37 ` Dongli Zhang
2019-04-04 16:18 ` Thomas Gleixner
2019-04-04 22:19 ` Ming Lei
2019-04-04 22:29 ` Keith Busch
2019-04-04 22:50 ` Ming Lei
2019-04-05 11:35 ` Thomas Gleixner
2019-04-06 14:29 ` Dongli Zhang
2019-04-06 15:31 ` Dongli Zhang
2019-04-06 16:12 ` fin4478 fin4478
2019-04-08 15:07 ` Keith Busch [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=20190408150750.GB32498@localhost.localdomain \
--to=kbusch@kernel.org \
/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