All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Dave Young <dyoung@redhat.com>
Cc: kexec@lists.infradead.org, nasa4836@gmail.com,
	linux-kernel@vger.kernel.org, d.hatayama@jp.fujitsu.com,
	Andrew Morton <akpm@linux-foundation.org>,
	vgoyal@redhat.com
Subject: Re: [PATCH] proc-vmcore: wrong data type casting fix
Date: Fri, 11 Mar 2016 16:31:33 +0800	[thread overview]
Message-ID: <20160311083133.GA3207@x1.redhat.com> (raw)
In-Reply-To: <20160311081501.GA9147@dhcp-128-65.nay.redhat.com>

On 03/11/16 at 04:15pm, Dave Young wrote:
> On i686 PAE enabled machine the contiguous physical area could be large
> and it can cause triming down variables in below calculation in
> read_vmcore() and mmap_vmcore():
> 
> 	tsz = min_t(size_t, m->offset + m->size - *fpos, buflen);
> 
> Then the real size passed down is not correct any more.
> Suppose m->offset + m->size - *fpos being truncated to 0, buflen >0 then
> we will get tsz = 0. It is of course not an expected result.
> 
> During out test there are two problems caused by it:
	  ~ our
> 1) read_vmcore will refuse to continue so makedumpfile fails.
> 2) mmap_vmcore will trigger BUG_ON() in remap_pfn_range().
> 
> Use unsigned long long in min_t instead so that the variables are not
> truncated.
> 
> Signed-off-by: Baoquan He <bhe@redhat.com>
> Signed-off-by: Dave Young <dyoung@redhat.com>
> ---
>  fs/proc/vmcore.c |    7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> --- linux-x86.orig/fs/proc/vmcore.c
> +++ linux-x86/fs/proc/vmcore.c
> @@ -231,7 +231,9 @@ static ssize_t __read_vmcore(char *buffe
>  
>  	list_for_each_entry(m, &vmcore_list, list) {
>  		if (*fpos < m->offset + m->size) {
> -			tsz = min_t(size_t, m->offset + m->size - *fpos, buflen);
> +			tsz = (size_t)min_t(unsigned long long,
> +					    m->offset + m->size - *fpos,
> +					    buflen);
>  			start = m->paddr + *fpos - m->offset;
>  			tmp = read_from_oldmem(buffer, tsz, &start, userbuf);
>  			if (tmp < 0)
> @@ -461,7 +463,8 @@ static int mmap_vmcore(struct file *file
>  		if (start < m->offset + m->size) {
>  			u64 paddr = 0;
>  
> -			tsz = min_t(size_t, m->offset + m->size - start, size);
> +			tsz = (size_t)min_t(unsigned long long,
> +					    m->offset + m->size - start, size);
>  			paddr = m->paddr + start - m->offset;
>  			if (vmcore_remap_oldmem_pfn(vma, vma->vm_start + len,
>  						    paddr >> PAGE_SHIFT, tsz,

_______________________________________________
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: Dave Young <dyoung@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, d.hatayama@jp.fujitsu.com,
	vgoyal@redhat.com, kexec@lists.infradead.org, nasa4836@gmail.com
Subject: Re: [PATCH] proc-vmcore: wrong data type casting fix
Date: Fri, 11 Mar 2016 16:31:33 +0800	[thread overview]
Message-ID: <20160311083133.GA3207@x1.redhat.com> (raw)
In-Reply-To: <20160311081501.GA9147@dhcp-128-65.nay.redhat.com>

On 03/11/16 at 04:15pm, Dave Young wrote:
> On i686 PAE enabled machine the contiguous physical area could be large
> and it can cause triming down variables in below calculation in
> read_vmcore() and mmap_vmcore():
> 
> 	tsz = min_t(size_t, m->offset + m->size - *fpos, buflen);
> 
> Then the real size passed down is not correct any more.
> Suppose m->offset + m->size - *fpos being truncated to 0, buflen >0 then
> we will get tsz = 0. It is of course not an expected result.
> 
> During out test there are two problems caused by it:
	  ~ our
> 1) read_vmcore will refuse to continue so makedumpfile fails.
> 2) mmap_vmcore will trigger BUG_ON() in remap_pfn_range().
> 
> Use unsigned long long in min_t instead so that the variables are not
> truncated.
> 
> Signed-off-by: Baoquan He <bhe@redhat.com>
> Signed-off-by: Dave Young <dyoung@redhat.com>
> ---
>  fs/proc/vmcore.c |    7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> --- linux-x86.orig/fs/proc/vmcore.c
> +++ linux-x86/fs/proc/vmcore.c
> @@ -231,7 +231,9 @@ static ssize_t __read_vmcore(char *buffe
>  
>  	list_for_each_entry(m, &vmcore_list, list) {
>  		if (*fpos < m->offset + m->size) {
> -			tsz = min_t(size_t, m->offset + m->size - *fpos, buflen);
> +			tsz = (size_t)min_t(unsigned long long,
> +					    m->offset + m->size - *fpos,
> +					    buflen);
>  			start = m->paddr + *fpos - m->offset;
>  			tmp = read_from_oldmem(buffer, tsz, &start, userbuf);
>  			if (tmp < 0)
> @@ -461,7 +463,8 @@ static int mmap_vmcore(struct file *file
>  		if (start < m->offset + m->size) {
>  			u64 paddr = 0;
>  
> -			tsz = min_t(size_t, m->offset + m->size - start, size);
> +			tsz = (size_t)min_t(unsigned long long,
> +					    m->offset + m->size - start, size);
>  			paddr = m->paddr + start - m->offset;
>  			if (vmcore_remap_oldmem_pfn(vma, vma->vm_start + len,
>  						    paddr >> PAGE_SHIFT, tsz,

  reply	other threads:[~2016-03-11  8:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11  8:15 [PATCH] proc-vmcore: wrong data type casting fix Dave Young
2016-03-11  8:15 ` Dave Young
2016-03-11  8:31 ` Baoquan He [this message]
2016-03-11  8:31   ` Baoquan He

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=20160311083133.GA3207@x1.redhat.com \
    --to=bhe@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nasa4836@gmail.com \
    --cc=vgoyal@redhat.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.