From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 3/3] IA64: verify the base address of crashkernel
Date: Wed, 07 Mar 2007 07:55:14 +0000 [thread overview]
Message-ID: <20070307075512.GA19315@verge.net.au> (raw)
In-Reply-To: <20070306073756.245032985@tabatha.lab.ultramonkey.org>
On Wed, Mar 07, 2007 at 12:50:12PM +0800, Zou, Nanhai wrote:
> On Wed, Mar 07, 2007 at 11:46, Horms wrote:
> >
> > I think that the manual option is also important because it
> > maintains feature-compatibility with other architectures. I don't
> > consider it a hack that might work purely for the purposes of
> > debugging.
>
> I don't understand why we need to maintain compatibility with other
> architectures here. Manfully choose may confuse user, XXX@16M may work
> on one arch,but not on another arch. Other architectures need manually
> choose crash kernel region simply because they do not support kernel
> automatically choose feature.
>
> I keep the XXX@YYY format to just make kdump script compatible, do
> that distributions does not need to maintain different kdump scripts
> for different arches.
From my point of view, what you say in the paragraph immediately above
is the crux of the point. There is a case for compatibility. And
furthermore, that compatibility really ought to be correct rather than a
bit of a hack. (Or in this case a bit more of a hack than the auto
select code path.)
> > With regards to 70 lines of extra code, it can probably be consolidated
> > a bit - for insance I think that the ckeck contained in
> > kdump_region_verify_rsvd_region() is more important than the other
> > checks which I guess could be disposed of if the length of the code
> > really is a problem. But in any case the new code is almost entirely in
> > __init. So I don't really see that it is a big concern.
> >
> > As for the partly-overlaped case in kdump_region_verify_rsvd_region().
> > I'm not entirely sure what you are getting at there. Are you talking
> > about an optimisation to the check, or a correctness problem?
> >
> (reserve_region.start < base && reserve_region.end < base + size)
> or
> (reserve_region.end > base && reserve_region.end > base + size) will pass the check
Thanks, is this logic better?
kdump_region_verify_rsvd_region (unsigned long base, unsigned long size,
struct rsvd_region *rsvd_regions, int n)
{
int i;
for (i = 0; i < n; i++) {
/* Assume that start < end && size > 0 */
if (__pa(rsvd_regions[i].start) >= base + size &&
__pa(rsvd_regions[i].end) < base)
continue;
printk(KERN_WARNING "Kdump: crashkernel region 0x%lx-0x%lx "
"clashes with reserved region 0x%lx-0x%lx\n", base,
base + size - 1, __pa(rsvd_regions[i].start),
__pa(rsvd_regions[i].end));
return 0;
}
return 1;
}
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
next prev parent reply other threads:[~2007-03-07 7:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 7:28 [patch 3/3] IA64: verify the base address of crashkernel Horms
2007-03-06 8:23 ` Zou, Nanhai
2007-03-06 17:08 ` Aron Griffis
2007-03-07 0:42 ` Horms
2007-03-07 0:50 ` Horms
2007-03-07 0:57 ` Horms
2007-03-07 2:15 ` Zou, Nanhai
2007-03-07 3:46 ` Horms
2007-03-07 4:50 ` Zou, Nanhai
2007-03-07 7:55 ` Horms [this message]
2007-03-07 9:06 ` Zou, Nanhai
2007-03-07 9:49 ` Horms
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=20070307075512.GA19315@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-ia64@vger.kernel.org \
/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