public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@openvz.org>
To: Miklos Szeredi <miklos@szeredi.hu>, riel@redhat.com
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	xemul@openvz.org, raven@themaw.net
Subject: Re: futex strangeness in 2.6.23-mm1/UML
Date: Tue, 23 Oct 2007 12:55:44 +0400	[thread overview]
Message-ID: <471DB710.1060603@openvz.org> (raw)
In-Reply-To: <E1IkEJP-0004Qp-00@dorka.pomaz.szeredi.hu>

Miklos Szeredi wrote:
>> I guess we can debug it in the old-fashioned ways.  The first of which is
>> to palm the problem off on Pavel ;)

I look at the 2.6.23-mm1 and see that there's one hunk lost. This
is the one Oleg re-sent some days ago (the mail thread subject was
2.6.23-mm1 thread exit_group issue). Here it is (sent 13 oct 2007):

--- kernel/fork.c~	2007-10-13 15:41:35.000000000 +0400
+++ kernel/fork.c	2007-10-13 15:41:41.000000000 +0400
@@ -1443,6 +1443,9 @@ long do_fork(unsigned long clone_flags,
 			task_pid_nr_ns(p, current->nsproxy->pid_ns) :
 				task_pid_vnr(p);
 
+		if (clone_flags & CLONE_PARENT_SETTID)
+			put_user(nr, parent_tidptr);
+
 		if (clone_flags & CLONE_VFORK) {
 			p->vfork_done = &vfork;
 			init_completion(&vfork);

Please, try with this patch.

>> I don't recall seeing a simple step-by-step way by which others can
>> reproduce this?
> 
> My method is this:
> 
> - enable CONFIG_FUSE_FS
> - compile fuse from CVS:
>  cvs -d:pserver:anonymous@fuse.cvs.sourceforge.net:/cvsroot/fuse co -P fuse
>  cd fuse
>  ./makeconf.sh
>  ./configure
>  make
>  make -C test
> 
> - in one shell:
>  mkdir /tmp/fuse
>  example/fusexmp_fh -d /tmp/fuse
> 
> - in another shell:
>  mkdir /tmp/test
>  test/test /tmp/fuse/tmp/test
> 
> The result is normally a completed run with "1 tests failed".  On
> 2.6.23-mm1, it just hangs after the first test.
> 
> I've only tried under UML, but since Rick is seeing it on real HW, I
> guess this method may work there as well.
> 
> Miklos
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  reply	other threads:[~2007-10-23  8:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 17:29 futex strangeness in 2.6.23-mm1/UML Miklos Szeredi
2007-10-22 18:53 ` Rik van Riel
2007-10-22 20:48   ` Miklos Szeredi
2007-10-22 21:29     ` Rik van Riel
2007-10-23  0:07       ` Rik van Riel
2007-10-23  0:16         ` Andrew Morton
2007-10-23  1:11           ` Rik van Riel
2007-10-23  1:38             ` Rik van Riel
2007-10-23  2:54               ` Ian Kent
2007-10-23  3:41               ` Jeff Dike
2007-10-23  7:36           ` Miklos Szeredi
2007-10-23  8:55             ` Pavel Emelyanov [this message]
2007-10-23 10:23               ` Miklos Szeredi
2007-10-23 13:52               ` Rik van Riel
2007-10-23 16:00                 ` 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=471DB710.1060603@openvz.org \
    --to=xemul@openvz.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=raven@themaw.net \
    --cc=riel@redhat.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