All of lore.kernel.org
 help / color / mirror / Atom feed
From: dyoung@redhat.com
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	d.hatayama@jp.fujitsu.com, bhe@redhat.com, vgoyal@redhat.com
Cc: kexec@lists.infradead.org, dyoung@redhat.com
Subject: [PATCH 0/2] min_t type casting bug fixes
Date: Fri, 11 Mar 2016 14:21:56 +0800	[thread overview]
Message-ID: <20160311062156.131015797@redhat.com> (raw)

Hi,

We found a min_t type casting issue in fs/proc/vmcore.c, it uses smaller
type in min_t so that during i386 PAE testing 64bit value was trucated
and then cause saving vmcore failure and BUG() for mmap case.

I introduced new macros min_lt and max_lt to select the larger data type
in x and y. Then use it in 2nd patch.

Any comments are appreciated.

Thanks
Dave


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

WARNING: multiple messages have this Message-ID (diff)
From: dyoung@redhat.com
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	d.hatayama@jp.fujitsu.com, bhe@redhat.com, vgoyal@redhat.com
Cc: dyoung@redhat.com, kexec@lists.infradead.org
Subject: [PATCH 0/2] min_t type casting bug fixes
Date: Fri, 11 Mar 2016 14:21:56 +0800	[thread overview]
Message-ID: <20160311062156.131015797@redhat.com> (raw)

Hi,

We found a min_t type casting issue in fs/proc/vmcore.c, it uses smaller
type in min_t so that during i386 PAE testing 64bit value was trucated
and then cause saving vmcore failure and BUG() for mmap case.

I introduced new macros min_lt and max_lt to select the larger data type
in x and y. Then use it in 2nd patch.

Any comments are appreciated.

Thanks
Dave

             reply	other threads:[~2016-03-11  6:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11  6:21 dyoung [this message]
2016-03-11  6:21 ` [PATCH 0/2] min_t type casting bug fixes dyoung

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