From: Minfei Huang <mhuang@redhat.com>
To: Baoquan He <bhe@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
ebiederm@xmission.com, vgoyal@redhat.com, dyoung@redhat.com,
lisa.mitchell@hp.com, tatsu@ab.jp.nec.com,
seiji.aguchi.tr@hitachi.com, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org
Subject: Re: [Patch v2] align crash_notes allocation to make it be inside one physical page
Date: Tue, 11 Aug 2015 16:01:08 +0800 [thread overview]
Message-ID: <20150811080108.GA2404@dhcp-128-25.nay.redhat.com> (raw)
In-Reply-To: <20150811063333.GB9748@dhcp-17-102.nay.redhat.com>
On 08/11/15 at 02:33pm, Baoquan He wrote:
> Hi Andrew,
>
> On 08/03/15 at 03:04pm, Andrew Morton wrote:
> > On Mon, 3 Aug 2015 20:50:43 +0800 Baoquan He <bhe@redhat.com> wrote:
> > And I think the WARN_ON can be replaced with a
> > BUILD_BUG_ON(sizeof>PAGE_SIZE)? That would avoid adding runtime
> > overhead.
>
> Rethink about this, you are right. Using BUILD_BUG_ON is better.
> Anyone who found this compiling break should check if his/her code
> changes increase the crash_notes size. If possible that increase need be
> avoidable. Otherwise he should report this to upstream why it's
> unavoidable to increase crash_notes size, then let's consider the
> redesign the crash_notes data structure.
>
> So I will use BUILD_BUG_ON and repost.
Baoquan.
If the size of notes never be exceeded to PAGE_SIZE, I think we can
revert below patch, since the situation which describes in patch does
not happen.
commit 38dfac843cb6d7be1874888839817404a15a6b3c
Author: Greg Pearson <greg.pearson@hp.com>
Date: Mon Feb 10 14:25:36 2014 -0800
vmcore: prevent PT_NOTE p_memsz overflow during header update
What do you think about this?
Thanks
Minfei
next prev parent reply other threads:[~2015-08-11 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 12:50 Baoquan He
2015-08-03 22:04 ` Andrew Morton
2015-08-03 23:01 ` Baoquan He
2015-08-11 6:33 ` Baoquan He
2015-08-11 8:01 ` Minfei Huang [this message]
2015-08-11 8:42 ` 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=20150811080108.GA2404@dhcp-128-25.nay.redhat.com \
--to=mhuang@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lisa.mitchell@hp.com \
--cc=seiji.aguchi.tr@hitachi.com \
--cc=tatsu@ab.jp.nec.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 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®