mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shivang Upadhyay <shivangu@linux.ibm.com>
To: Mukesh Kumar Chaurasiya <mkchauras@gmail.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	sourabhjain@linux.ibm.com, adityag@linux.ibm.com,
	adri.vero.dev@gmail.com, anushree.mathur@linux.vnet.ibm.com,
	chleroy@kernel.org, maddy@linux.ibm.com, mpe@ellerman.id.au,
	npiggin@gmail.com
Subject: Re: [PATCH v4] ppc/fadump: collect dump when CPU_STATE_DATA is less than reserved
Date: Thu, 24 Sep 2026 18:56:01 +0530	[thread overview]
Message-ID: <a18fbf8f3923f14215006a23a5a94dae63ab3ae9.camel@linux.ibm.com> (raw)
In-Reply-To: <arTuiz2iOQkPdHwT@li-1a3e774c-28e4-11b2-a85c-acc9f2883e29.ibm.com>

On Thu, 2026-09-24 at 15:06 +0530, Mukesh Kumar Chaurasiya wrote:
> > +			 */
> > +			if (!(bytes_dumped == source_len ||
> > +			(type == RTAS_FADUMP_CPU_STATE_DATA &&
> > bytes_dumped <= source_len))) {
> > +
> Extra line here.
I'll fix this in next revision.

> >   				pr_err("Dump taken by platform is
> > incomplete (%d)\n", i);
> > +				pr_debug("type -> %d, bytes_dumped
> > -> %llx, source_len -> %llx\n",
> > +					 type, bytes_dumped,
> > source_len);
> >   				rc = -EINVAL;
> >   			}
> Can bytes_dumped be greater than source_len? 
> If yes then the error is misinformed that it's incomplete instead
> it's corrupted.
> If No then shouldn't the internal check bytes_dumped <= source_len
> should handle it?
> 
Yes, It can be more. The wording on error here can be better. I should
change that in next revision.

Thanks for your review.

~Shivang.
> 

      reply	other threads:[~2026-09-24 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28  9:49 Shivang Upadhyay
2026-09-12 12:33 ` Sourabh Jain
2026-09-23 16:21 ` Anushree Mathur
2026-09-24 13:27   ` Shivang Upadhyay
2026-09-24  9:36 ` Mukesh Kumar Chaurasiya
2026-09-24 13:26   ` Shivang Upadhyay [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=a18fbf8f3923f14215006a23a5a94dae63ab3ae9.camel@linux.ibm.com \
    --to=shivangu@linux.ibm.com \
    --cc=adityag@linux.ibm.com \
    --cc=adri.vero.dev@gmail.com \
    --cc=anushree.mathur@linux.vnet.ibm.com \
    --cc=chleroy@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mkchauras@gmail.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=sourabhjain@linux.ibm.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

all inboxes | Powered by JetHome®