From: "Łukasz Michalik" <lmi@ift.uni.wroc.pl>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
Denys Vlasenko <vda.linux@googlemail.com>,
Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org,
"Dmitry V. Levin" <ldv@altlinux.org>
Subject: Re: ptrace fixes for 3.2
Date: Wed, 4 Jan 2012 10:00:52 +0100 [thread overview]
Message-ID: <20120104090052.GA24624@havoc.ift.uni.wroc.pl> (raw)
In-Reply-To: <4F033227.3020404@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
On 17:51 2012-01-03 +0100, Denys Vlasenko wrote:
> On 01/03/2012 04:44 PM, Oleg Nesterov wrote:
> >On 01/03, Oleg Nesterov wrote:
> >>
> >>I am going to send the hack^Wpatch below to Linus as a temporary
> >>workaround for 3.2.
> >
> >The same patch with the changelog.
> >
> >Denys, Tejun, any chance you can review it before I send it to Linus ?
>
> Testing it on top of Fedora 16's kernel-3.1.6-1.fc16:
>
> Confirmed that before patch both tests fail (in about a minute of run time
> at worst), and with patch they do not fail.
>
Tested on top vanilla's HEAD and stable 3.1.7, with both testcases and
both strace and sydbox. Confirming same as Denys.
--
Pozdrawiam,
Łukasz P. Michalik
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-01-04 9:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 18:55 Possible bug introduced in commit 9b84cca Denys Vlasenko
2011-12-28 21:07 ` Denys Vlasenko
2011-12-28 21:23 ` Łukasz Michalik
2011-12-29 11:32 ` Oleg Nesterov
2011-12-29 12:05 ` Oleg Nesterov
2012-01-03 14:29 ` Oleg Nesterov
2012-01-03 15:44 ` ptrace fixes for 3.2 Oleg Nesterov
2012-01-03 16:30 ` Tejun Heo
2012-01-03 17:09 ` Oleg Nesterov
2012-01-03 19:18 ` Tejun Heo
2012-01-04 11:35 ` Oleg Nesterov
2012-01-04 15:31 ` Tejun Heo
2012-01-04 15:59 ` Oleg Nesterov
2012-01-03 16:51 ` Denys Vlasenko
2012-01-04 9:00 ` Łukasz Michalik [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=20120104090052.GA24624@havoc.ift.uni.wroc.pl \
--to=lmi@ift.uni.wroc.pl \
--cc=dvlasenk@redhat.com \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=tj@kernel.org \
--cc=vda.linux@googlemail.com \
/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
all inboxes | Powered by JetHome®