lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6599ad830611300051q5f48fb45gbfae9649e0e14524@mail.gmail.com>
Date:	Thu, 30 Nov 2006 00:51:26 -0800
From:	"Paul Menage" <menage@...gle.com>
To:	"Paul Jackson" <pj@....com>
Cc:	akpm@...l.org, sekharan@...ibm.com, dev@...ru, xemul@...ru,
	linux-kernel@...r.kernel.org, ckrm-tech@...ts.sourceforge.net,
	devel@...nvz.org, mbligh@...gle.com, winget@...gle.com,
	rohitseth@...gle.com
Subject: Re: [PATCH 0/7] Generic Process Containers (+ ResGroups/BeanCounters)

On 11/29/06, Paul Jackson <pj@....com> wrote:
>
> 2) I wedged the kernel on the container_lock, doing a removal of a cpuset
>    using notify_on_release.

I couldn't reproduce this, with a /sbin/cpuset_release_agent that does:

#!/bin/bash
logger cpuset_release_agent $1
rmdir /dev/cpuset/$1

and running the commands:

while true; do
  mkdir -p /dev/cpuset/bar/foo
  echo 1 > /dev/cpuset/bar/notify_on_release
  rmdir /dev/cpuset/bar/foo
  usleep 1000
done

Is it actually reproducible for you? If so, could you get a fuller backtrace?

Thanks,

Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ