public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Ben Dooks <ben@fluff.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	hvr@gnu.org, rmk@arm.linux.org.uk, nico@cam.org
Subject: Re: [PATCH] ARM: Ignore memory tags with invalid data
Date: Tue, 22 Jan 2008 08:34:10 -0600	[thread overview]
Message-ID: <4795FEE2.3090703@acm.org> (raw)
In-Reply-To: <20080122091834.GC27399@fluff.org.uk>

Ben Dooks wrote:
> On Mon, Jan 21, 2008 at 10:05:56PM -0600, Corey Minyard wrote:
>   
>> From: Corey Minyard <minyard@acm.org>
>>
>> The DNS-323 system has several bogus memory entries in the tag table,
>> and it caused the system to crash at startup.  Ignore tag entries that
>> are obviously bogus.
>>     
>
> This should have gone to the linux-arm-kernel mailing list as well,
> so that all the people interested in ARM can see it as soon as
> possible. See linux-arm-kernel@lists.arm.linux.org.uk
>   
You have to be a member to post, and I'm not a member.  I guess I'll 
join, though it seems somewhat pointless for a single patch.

> The only suggestion I could think of would to be change to having
> an check_tag_mem32() function, or put each check on its own line
> to make it easier to read what each check is doing.
>
> ie:
> 	if (meminfo.nr_banks >= NR_BANKS ||
> 	    tag->u.mem.size & ~PAGE_MASK || /* size is unaligned */
> 	    tag->u.mem.size == 0 ||	    /* no memory here */
> 	    tag->u.mem.start & ~PAGE_MASK)  /* start is unaligned */ 
> 	{
>
> (even without the comments it makes it easier to see what each test
> is.
>   
That's fine, it is easier to read.

Thanks,

-corey

  reply	other threads:[~2008-01-22 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22  4:05 [PATCH] ARM: Ignore memory tags with invalid data Corey Minyard
2008-01-22  9:18 ` Ben Dooks
2008-01-22 14:34   ` Corey Minyard [this message]
2008-01-22 19:53     ` Russell King
2008-02-10 21:11 ` Byron Bradley

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=4795FEE2.3090703@acm.org \
    --to=minyard@acm.org \
    --cc=ben@fluff.org \
    --cc=hvr@gnu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@cam.org \
    --cc=rmk@arm.linux.org.uk \
    /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