public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zhoujian (jay)" <jianjay.zhou@huawei.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"tj@kernel.org" <tj@kernel.org>,
	"Huangweidong (C)" <weidong.huang@huawei.com>,
	"Wangjing(Hogan)" <hogan.wang@huawei.com>
Subject: RE: [Question] kernfs: NULL pointer dereference in kernfs_dop_revalidate()
Date: Mon, 28 Mar 2022 15:23:43 +0000	[thread overview]
Message-ID: <9ed26568de294a6892806df779908d4c@huawei.com> (raw)
In-Reply-To: <YkGn5EU3mkUha2U6@kroah.com>

> -----Original Message-----
> From: gregkh@linuxfoundation.org [mailto:gregkh@linuxfoundation.org]
> Sent: Monday, March 28, 2022 8:20 PM
> To: Zhoujian (jay) <jianjay.zhou@huawei.com>
> Cc: linux-kernel@vger.kernel.org; tj@kernel.org; Huangweidong (C)
> <weidong.huang@huawei.com>; Wangjing(Hogan) <hogan.wang@huawei.com>
> Subject: Re: [Question] kernfs: NULL pointer dereference in
> kernfs_dop_revalidate()
> 
> On Mon, Mar 28, 2022 at 11:59:49AM +0000, Zhoujian (jay) wrote:
> > Hi,
> >
> > We met a kernel panic during boot the new kernel using kexec, the
> > kernel version is 4.18.0(with some our changes), here is the stack:
> 
> 4.18.0 is _VERY_ old and obsolete, sorry.  Can you duplicate this on 5.17?

Thanks for your reply, I'll have a try.

      reply	other threads:[~2022-03-28 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 11:59 [Question] kernfs: NULL pointer dereference in kernfs_dop_revalidate() Zhoujian (jay)
2022-03-28 12:19 ` gregkh
2022-03-28 15:23   ` Zhoujian (jay) [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=9ed26568de294a6892806df779908d4c@huawei.com \
    --to=jianjay.zhou@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hogan.wang@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=weidong.huang@huawei.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