From: Bjorn Helgaas <helgaas@kernel.org>
To: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"mika.westerberg@linux.intel.com"
<mika.westerberg@linux.intel.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"logang@deltatee.com" <logang@deltatee.com>,
Naresh Kamboju <naresh.kamboju@linaro.org>
Subject: Re: [PATCH v3 1/1] PCI: Fix bug resulting in double hpmemsize being assigned to MMIO window
Date: Thu, 21 Nov 2019 11:55:07 -0600 [thread overview]
Message-ID: <20191121175507.GA54569@google.com> (raw)
In-Reply-To: <PSXP216MB043824FACB1E66E3F31890D2804E0@PSXP216MB0438.KORP216.PROD.OUTLOOK.COM>
[+cc Naresh]
On Thu, Nov 21, 2019 at 02:52:41PM +0000, Nicholas Johnson wrote:
> On Tue, Nov 19, 2019 at 07:38:28AM -0600, Bjorn Helgaas wrote:
> > On Tue, Nov 19, 2019 at 03:17:04AM +0000, Nicholas Johnson wrote:
> > > I did just discover linux-next and I built it. Should I be doing this
> > > more often to help find regressions?
> >
> > Yes, if you build and run linux-next, that's a great service because
> > it helps find problems before they appear in mainline.
>
> Funnily enough, I just built Linux next-20191121 and it has a NULL
> dereference on start-up, which renders the system unusable.
>
> Can anybody else please confirm? I enabled most of the new options since
> the last linux-next a few days before.
> ...
> Here is a preliminary bug report (assuming you are meant to report
> linux-next bugs here):
> https://bugzilla.kernel.org/show_bug.cgi?id=205621
Looks similar to these reports I found by searching for kernfs_find_ns on
https://lore.kernel.org/lkml:
https://lore.kernel.org/r/000000000000bdfc8e0597ddbde4@google.com
https://lore.kernel.org/r/000000000000c1e9090597ddbd9d@google.com
https://lore.kernel.org/r/CA+G9fYsrRw2SRb92eROCt6aU==j6Qr9Fe4AmJyn4fMj5gDFt=w@mail.gmail.com
Thanks very much for doing this testing and reporting the results. I
don't think there's anything more you need to do. It looks like
Naresh already cc'd some likely candidates.
Bjorn
prev parent reply other threads:[~2019-11-21 17:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 15:25 [PATCH v3 1/1] PCI: Fix bug resulting in double hpmemsize being assigned to MMIO window Nicholas Johnson
2019-11-13 16:50 ` Logan Gunthorpe
2019-11-14 16:56 ` Bjorn Helgaas
2019-11-16 2:54 ` Nicholas Johnson
2019-11-18 9:43 ` Nicholas Johnson
2019-11-18 22:58 ` Bjorn Helgaas
2019-11-19 3:17 ` Nicholas Johnson
2019-11-19 13:38 ` Bjorn Helgaas
2019-11-21 14:52 ` Nicholas Johnson
2019-11-21 17:55 ` Bjorn Helgaas [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=20191121175507.GA54569@google.com \
--to=helgaas@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=mika.westerberg@linux.intel.com \
--cc=naresh.kamboju@linaro.org \
--cc=nicholas.johnson-opensource@outlook.com.au \
/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;
as well as URLs for NNTP newsgroup(s).