The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, mingo@elte.hu,
	trini@kernel.crashing.org
Subject: Re: [patch 1/2] Validate itimer timeval from userspace
Date: Sat, 18 Mar 2006 21:30:20 +0100	[thread overview]
Message-ID: <1142713820.17279.140.camel@localhost.localdomain> (raw)
In-Reply-To: <9a8748490603181223i32391d96nf794e93aa734f785@mail.gmail.com>

On Sat, 2006-03-18 at 21:23 +0100, Jesper Juhl wrote:

> Wouldn't this only break existing applications that do incorrect
> things (passing invalid values) ?
> If that's the case I'd say breaking them is OK and we should change to
> follow the spec.
> 
> I don't like potential userspace breakage any more than the next guy,
> but if the breakage only affects buggy applications then I think it's
> more acceptable.

Yes, it only breaks buggy applications.

On a full blown desktop the check (I added a printk) did not trigger.

The only application I found so far was the LTP setitimer "correctness"
test, which did not initialize it_interval and handed random garbage to
the kernel. :)

	tglx



  reply	other threads:[~2006-03-18 20:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-18 15:18 [patch 0/2] sys_setitimer and sys_alarm hotfixes Thomas Gleixner
2006-03-18 15:18 ` [patch 1/2] Validate itimer timeval from userspace Thomas Gleixner
2006-03-18 19:10   ` Ingo Molnar
2006-03-18 19:57     ` Thomas Gleixner
2006-03-18 20:07   ` Andrew Morton
2006-03-18 20:16     ` Thomas Gleixner
2006-03-18 20:31       ` Andrew Morton
2006-03-18 20:38         ` Thomas Gleixner
2006-03-18 21:09           ` Andrew Morton
2006-03-18 21:26             ` Jesper Juhl
2006-03-18 21:33               ` Andrew Morton
2006-03-18 21:50                 ` Jesper Juhl
2006-03-18 22:05             ` Thomas Gleixner
2006-03-18 22:25               ` Andrew Morton
2006-03-18 23:12                 ` tglx
2006-03-18 20:45         ` Jesper Juhl
2006-03-18 22:02           ` Ray Lee
2006-03-18 23:14           ` Eric Piel
2006-03-19  8:55             ` Kyle Moffett
2006-03-18 20:23     ` Jesper Juhl
2006-03-18 20:30       ` Thomas Gleixner [this message]
2006-03-18 21:04         ` Andrew Morton
2006-03-21 15:31           ` Pavel Machek
2006-03-18 15:18 ` [patch 2/2] alarm unsigned signed conversion fixup Thomas Gleixner
2006-03-18 20:02   ` Thomas Gleixner
2006-03-18 20:12   ` Andrew Morton
2006-03-18 20:27     ` Thomas Gleixner
2006-03-18 21:06       ` Andrew Morton

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=1142713820.17279.140.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=akpm@osdl.org \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=trini@kernel.crashing.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