All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: "yang.zhang" <gaoshanliukou@163.com>
Cc: ebiederm@xmission.com, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	"yang.zhang" <yang.zhang@hexintek.com>
Subject: Re: [PATCH] kexec: should use uchunk for user buffer increasing
Date: Sun, 4 Feb 2024 15:38:26 +0800	[thread overview]
Message-ID: <Zb8+8qmn5SV4LKFd@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20240130101802.23850-1-gaoshanliukou@163.com>

On 01/30/24 at 06:18pm, yang.zhang wrote:
> From: "yang.zhang" <yang.zhang@hexintek.com>
> 
> Because of alignment requirement in kexec-tools, there is
> no problem for user buffer increasing when loading segments.
> But when coping, the step is uchunk, so we should use uchunk
> not mchunk.

In theory, ubytes is <= mbytes. So uchunk is always <= mchunk. If ubytes
is exhausted, while there's still remaining mbytes, then uchunk is 0,
there's still mchunk stepping forward. If I understand it correctly,
this is a good catch. Not sure if Eric has comment on this to confirm.

static int kimage_load_normal_segment(struct kimage *image,
                                         struct kexec_segment *segment)
{
......

                ptr += maddr & ~PAGE_MASK;
                mchunk = min_t(size_t, mbytes,
                                PAGE_SIZE - (maddr & ~PAGE_MASK));
                uchunk = min(ubytes, mchunk);
......}

> 
> Signed-off-by: yang.zhang <yang.zhang@hexintek.com>
> ---
>  kernel/kexec_core.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c
> index d08fc7b5db97..2b8354313c85 100644
> --- a/kernel/kexec_core.c
> +++ b/kernel/kexec_core.c
> @@ -813,9 +813,9 @@ static int kimage_load_normal_segment(struct kimage *image,
>  		ubytes -= uchunk;
>  		maddr  += mchunk;
>  		if (image->file_mode)
> -			kbuf += mchunk;
> +			kbuf += uchunk;
>  		else
> -			buf += mchunk;
> +			buf += uchunk;
>  		mbytes -= mchunk;
>  
>  		cond_resched();
> @@ -881,9 +881,9 @@ static int kimage_load_crash_segment(struct kimage *image,
>  		ubytes -= uchunk;
>  		maddr  += mchunk;
>  		if (image->file_mode)
> -			kbuf += mchunk;
> +			kbuf += uchunk;
>  		else
> -			buf += mchunk;
> +			buf += uchunk;
>  		mbytes -= mchunk;
>  
>  		cond_resched();
> -- 
> 2.34.1
> 
> 
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
> 


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: "yang.zhang" <gaoshanliukou@163.com>
Cc: ebiederm@xmission.com, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	"yang.zhang" <yang.zhang@hexintek.com>
Subject: Re: [PATCH] kexec: should use uchunk for user buffer increasing
Date: Sun, 4 Feb 2024 15:38:26 +0800	[thread overview]
Message-ID: <Zb8+8qmn5SV4LKFd@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20240130101802.23850-1-gaoshanliukou@163.com>

On 01/30/24 at 06:18pm, yang.zhang wrote:
> From: "yang.zhang" <yang.zhang@hexintek.com>
> 
> Because of alignment requirement in kexec-tools, there is
> no problem for user buffer increasing when loading segments.
> But when coping, the step is uchunk, so we should use uchunk
> not mchunk.

In theory, ubytes is <= mbytes. So uchunk is always <= mchunk. If ubytes
is exhausted, while there's still remaining mbytes, then uchunk is 0,
there's still mchunk stepping forward. If I understand it correctly,
this is a good catch. Not sure if Eric has comment on this to confirm.

static int kimage_load_normal_segment(struct kimage *image,
                                         struct kexec_segment *segment)
{
......

                ptr += maddr & ~PAGE_MASK;
                mchunk = min_t(size_t, mbytes,
                                PAGE_SIZE - (maddr & ~PAGE_MASK));
                uchunk = min(ubytes, mchunk);
......}

> 
> Signed-off-by: yang.zhang <yang.zhang@hexintek.com>
> ---
>  kernel/kexec_core.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c
> index d08fc7b5db97..2b8354313c85 100644
> --- a/kernel/kexec_core.c
> +++ b/kernel/kexec_core.c
> @@ -813,9 +813,9 @@ static int kimage_load_normal_segment(struct kimage *image,
>  		ubytes -= uchunk;
>  		maddr  += mchunk;
>  		if (image->file_mode)
> -			kbuf += mchunk;
> +			kbuf += uchunk;
>  		else
> -			buf += mchunk;
> +			buf += uchunk;
>  		mbytes -= mchunk;
>  
>  		cond_resched();
> @@ -881,9 +881,9 @@ static int kimage_load_crash_segment(struct kimage *image,
>  		ubytes -= uchunk;
>  		maddr  += mchunk;
>  		if (image->file_mode)
> -			kbuf += mchunk;
> +			kbuf += uchunk;
>  		else
> -			buf += mchunk;
> +			buf += uchunk;
>  		mbytes -= mchunk;
>  
>  		cond_resched();
> -- 
> 2.34.1
> 
> 
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
> 


  reply	other threads:[~2024-02-04  7:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 10:18 [PATCH] kexec: should use uchunk for user buffer increasing yang.zhang
2024-01-30 10:18 ` yang.zhang
2024-02-04  7:38 ` Baoquan He [this message]
2024-02-04  7:38   ` Baoquan He
2024-02-05 12:27   ` Eric W. Biederman
2024-02-05 12:27     ` Eric W. Biederman
2024-02-05 12:59     ` Baoquan He
2024-02-05 12:59       ` Baoquan He
2024-02-19  2:00     ` yang.zhang
2024-02-19  2:00       ` yang.zhang
2024-02-19  2:38       ` Baoquan He
2024-02-19  2:38         ` Baoquan He
2024-02-19  9:26         ` yang.zhang
2024-02-19  9:26           ` yang.zhang

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=Zb8+8qmn5SV4LKFd@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=gaoshanliukou@163.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yang.zhang@hexintek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.