On Wed, Aug 22, 2007 at 04:17:10PM -0700, Paul Menage wrote:
>
> I think this is the right way to handle the lockdep false-positive in
> the current containers patches, but I'm not that familiar with lockdep
> so any suggestions for a better approach are welcomed.
>
>
> In order to avoid a false
I think this is the right way to handle the lockdep false-positive in
the current containers patches, but I'm not that familiar with lockdep
so any suggestions for a better approach are welcomed.
In order to avoid a false-positive lockdep warning, we lock the root
inode of a new filesystem mount
On Wed, 22 Aug 2007 13:33:22 +0400
Pavel Emelyanov <[EMAIL PROTECTED]> wrote:
> The task_struct->pid member is going to be deprecated, so start
> using the helpers (task_pid_nr/task_pid_vnr/task_pid_nr_ns) in
> the kernel.
>
> The first thing to start with is the pid, printed to dmesg - in
> th
Paul Menage wrote:
> On 8/22/07, Balbir Singh <[EMAIL PROTECTED]> wrote:
>>
>> Signed-off-by: Balbir Singh <[EMAIL PROTECTED]>
>> ---
>>
>> Documentation/memcontrol.txt | 193
>> +++
>> 1 file changed, 193 insertions(+)
>>
>> diff -puN /dev/null Documentat
On 8/22/07, Balbir Singh <[EMAIL PROTECTED]> wrote:
>
>
> Signed-off-by: Balbir Singh <[EMAIL PROTECTED]>
> ---
>
> Documentation/memcontrol.txt | 193
> +++
> 1 file changed, 193 insertions(+)
>
> diff -puN /dev/null Documentation/memcontrol.txt
> --- /de
Randy Dunlap wrote:
> On Wed, 22 Aug 2007 18:36:12 +0530 Balbir Singh wrote:
>
>> Documentation/memcontrol.txt | 193
>> +++
>
> Is there some sub-dir that is appropriate for this, such as
> vm/ or accounting/ or containers/ (new) ?
>
>
Hi, Randy,
T
On Wed, 22 Aug 2007 18:36:12 +0530 Balbir Singh wrote:
> Documentation/memcontrol.txt | 193
> +++
Is there some sub-dir that is appropriate for this, such as
vm/ or accounting/ or containers/ (new) ?
> 1 file changed, 193 insertions(+)
>
> diff -puN
Tejun Heo <[EMAIL PROTECTED]> writes:
> Hello,
>
> Eric W. Biederman wrote:
>>> * fix-i_mutex-locking-in-sysfs_get_dentry patch is added at the top
>>> and #14-Don_t-use-lookup_one_len_kern and
>>> #15-vfs-Remove-lookup_one_len_kern are dropped. This is because #14
>>> contained had a bug w
Hello,
Eric W. Biederman wrote:
>> * fix-i_mutex-locking-in-sysfs_get_dentry patch is added at the top
>> and #14-Don_t-use-lookup_one_len_kern and
>> #15-vfs-Remove-lookup_one_len_kern are dropped. This is because #14
>> contained had a bug where it might created dentry/inode for an
>> a
Tejun Heo <[EMAIL PROTECTED]> writes:
> Hello, all.
>
> This is subset of Eric W. Biederman's "Sysfs cleanups & tagged
> directory support" patchset[1] with the following modifications.
As a base:
Acked-by: "Eric W. Biederman" <[EMAIL PROTECTED]>
>
> * fix-i_mutex-locking-in-sysfs_get_dentry pa
Signed-off-by: Balbir Singh <[EMAIL PROTECTED]>
---
Documentation/memcontrol.txt | 193 +++
1 file changed, 193 insertions(+)
diff -puN /dev/null Documentation/memcontrol.txt
--- /dev/null 2007-06-01 20:42:04.0 +0530
+++ linux-2.6.23-rc2-mm2-b
Cornelia Huck wrote:
> On Mon, 20 Aug 2007 21:36:29 +0900,
> Tejun Heo <[EMAIL PROTECTED]> wrote:
>
>> Hello, all.
>>
>> This is subset of Eric W. Biederman's "Sysfs cleanups & tagged
>> directory support" patchset[1] with the following modifications.
>>
>> * fix-i_mutex-locking-in-sysfs_get_dentr
The task_struct->pid member is going to be deprecated, so start
using the helpers (task_pid_nr/task_pid_vnr/task_pid_nr_ns) in
the kernel.
The first thing to start with is the pid, printed to dmesg - in
this case we may safely use task_pid_nr(). Besides, printks produce
more (much more) than
On Mon, 20 Aug 2007 21:36:29 +0900,
Tejun Heo <[EMAIL PROTECTED]> wrote:
> Hello, all.
>
> This is subset of Eric W. Biederman's "Sysfs cleanups & tagged
> directory support" patchset[1] with the following modifications.
>
> * fix-i_mutex-locking-in-sysfs_get_dentry patch is added at the top
>
14 matches
Mail list logo