public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peter Enderborg <Peter.Enderborg@sony.com>
Cc: Mark Brown <broonie@kernel.org>, Yingsha Xu <ysxu@hust.edu.cn>,
	Serge Semin <fancer.lancer@gmail.com>,
	linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: remove return value check of debugfs_create_dir()
Date: Mon, 24 Apr 2023 15:22:53 +0200	[thread overview]
Message-ID: <2023042431-crook-stable-5749@gregkh> (raw)
In-Reply-To: <3164e897-a423-3948-d50a-f2bdd4ad05e9@sony.com>

On Mon, Apr 24, 2023 at 03:17:09PM +0200, Peter Enderborg wrote:
> On 4/24/23 14:53, Greg Kroah-Hartman wrote:
> >
> >>> We can do things with the debug information without filesystem enabled.
> > What exactly do you mean by this?
> >
> >
> We can read out data from kernel with a ramdumper and analyse with crash.
> 
> See https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/kernel_administration_guide/kernel_crash_dump_guide
> 
> If it is useful or not I can not say, but the dws->regset. is lost and can not be read with a post mortem debugger.

What is "dws"?  What is "regset"?

What is the root problem here?

confused,

greg k-h

  reply	other threads:[~2023-04-24 13:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23  6:11 [PATCH] spi: remove return value check of debugfs_create_dir() Yingsha Xu
2023-04-24 11:54 ` Mark Brown
2023-04-24 12:20   ` Peter Enderborg
2023-04-24 12:32     ` Mark Brown
2023-04-24 12:53       ` Greg Kroah-Hartman
2023-04-24 13:00         ` Mark Brown
2023-04-24 13:08           ` Greg Kroah-Hartman
2023-04-24 13:17             ` Mark Brown
2023-04-24 13:17         ` Peter Enderborg
2023-04-24 13:22           ` Greg Kroah-Hartman [this message]
2023-04-24 13:54             ` Peter Enderborg
2023-04-25  5:31               ` Greg Kroah-Hartman

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=2023042431-crook-stable-5749@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Peter.Enderborg@sony.com \
    --cc=broonie@kernel.org \
    --cc=fancer.lancer@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=ysxu@hust.edu.cn \
    /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