public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: akpm@linux-foundation.org, hpa@zytor.com, tglx@linutronix.de,
	andi@firstfloor.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 0/5] early params NULL pointer deref fix
Date: Wed, 9 Jul 2008 19:25:05 +0400	[thread overview]
Message-ID: <20080709152505.GA6784@asus> (raw)
In-Reply-To: <20080709115746.GA19060@elte.hu>

[Ingo Molnar - Wed, Jul 09, 2008 at 01:57:48PM +0200]
| 
| * Cyrill Gorcunov <gorcunov@gmail.com> wrote:
| 
| >  This series fix a possible NULL pointer deref in case if user was 
| > stupid enough to pass boot parameter without a mandatory value
| > 
| >  Actually there is a number of such issues on other platforms too 
| > (like powerpc, sh, s390) so I think it should be fixed too (any 
| > volunteers?)
| > 
| >  Any comments are welcome.
| 
| thanks Cyrill, i picked them up.
| 
| I'm wondering, would it be possible to filter NULL out on one higher 
| level? Would it break any existing functionality? (i dont think it would 
| or should)
| 
| 	Ingo
| 

well, actually it would and should :)

Currently parser does a simple thing - just parses command line and split
key/param pairs. But kernel code uses it in three ways:

 1) as simple flag specified on booting
 2) as key and value
 3) combination of 1) and 2)

So for now I don't see any simple solution for this. We could use '='
param postfix to specify that a mandatory value required for param and
throw out any misconfigured boot options but it will make way 3) invalid
so kernel code will have to be fixed then. So some additional review
and conversation about this are needed.

		- Cyrill -

      reply	other threads:[~2008-07-09 15:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-05 11:53 [patch 0/5] early params NULL pointer deref fix Cyrill Gorcunov
2008-07-09 11:57 ` Ingo Molnar
2008-07-09 15:25   ` Cyrill Gorcunov [this message]

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=20080709152505.GA6784@asus \
    --to=gorcunov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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