From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: tglx@linutronix.de, jesper.juhl@gmail.com,
linux-kernel@vger.kernel.org, mingo@elte.hu,
trini@kernel.crashing.org
Subject: Re: [patch 1/2] Validate itimer timeval from userspace
Date: Tue, 21 Mar 2006 15:31:57 +0000 [thread overview]
Message-ID: <20060321153157.GA2500@ucw.cz> (raw)
In-Reply-To: <20060318130446.18f4ae40.akpm@osdl.org>
Hi!
> > > 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.
>
> But we live in the real world. There could be four-year-old applications
> which passed all their Linux QA and which work perfectly well.
>
> Then the kernel guys make some correctness change and that application
> totally fails on new kernels. Your choice is a) don't use new kernels or
> b) hold off the new kernel until your provider (if the company or internal
> group still exists) has put out a new version of the application and then
> you wear the (considerable) cost of upgrading what was a perfectly-running
> application.
>
> And whose fault was it? Ours. Because older kernels had the wrong
> checking (thus causing that app's QA to pass) and because later kernels
> changed the rules.
Can we do printk now and fix it after a while in feature-removal?
Or maybe we shoul create new bug-removal file :-).
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2006-03-23 16:21 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
2006-03-18 21:04 ` Andrew Morton
2006-03-21 15:31 ` Pavel Machek [this message]
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=20060321153157.GA2500@ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.