From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Mike Frysinger <vapier@gentoo.org>, <libc-ports@sourceware.org>
Subject: Re: [PATCH][BZ #15054] MIPS: Fix syscall wrappers for syscall restart support
Date: Tue, 29 Jan 2013 19:12:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1301291907520.4409@tp.orcam.me.uk> (raw)
In-Reply-To: <20130129190418.GC24911@linux-mips.org>
On Tue, 29 Jan 2013, Ralf Baechle wrote:
> > > sure, you won't be able to retroactively fixing kernels. but you'll be able to
> > > make future kernels more robust against shady userlands. as you've pointed
> > > out, this is an extremely subtle bug that can easily go unnoticed for a long
> > > time which simply injects random flakiness into the runtime system.
> >
> > That's not unreasonable, I agree. Ralf, what do you think?
>
> Kernel commit 8f5a00eb422ed86e77bb8f67e08b9fe6d30f679a [MIPS: Sanitize
> restart logics] dated September 28, 2010 has already fixed this issue
> for Linux 2.6.36.
>
> The linux-mips.org kernel tree contains backports of this patch to all
> -stable branches all the way back to 2.6.16.
Good to know, thanks. This means we won't have to be concerned about
this issue once we have stopped supporting kernel versions below 2.6.36.
Maciej
next prev parent reply other threads:[~2013-01-29 19:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 3:09 Maciej W. Rozycki
2013-01-23 5:05 ` Mike Frysinger
2013-01-23 5:40 ` Maciej W. Rozycki
2013-01-23 18:13 ` Mike Frysinger
2013-01-29 18:12 ` Maciej W. Rozycki
2013-01-29 19:04 ` Ralf Baechle
2013-01-29 19:12 ` Maciej W. Rozycki [this message]
2013-01-30 1:26 ` Ralf Baechle
2013-01-30 6:50 ` Mike Frysinger
2013-01-23 17:06 ` Joseph S. Myers
2013-01-24 12:47 ` Maciej W. Rozycki
2013-01-24 16:31 ` Joseph S. Myers
2013-01-29 18:10 ` Maciej W. Rozycki
2013-01-29 23:59 ` Joseph S. Myers
2013-02-05 15:26 ` Maciej W. Rozycki
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=alpine.DEB.1.10.1301291907520.4409@tp.orcam.me.uk \
--to=macro@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=ralf@linux-mips.org \
--cc=vapier@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).