Re: kernel lock in dcache.c

2001-04-28 Thread Alexander Viro



On Sat, 28 Apr 2001, Mark Hemment wrote:

> Hi,
> 
>   d_move() in fs/dcache.c is checking the kernel lock is held
> (switch_names() does the same, but is only called from d_move()).
> 
>   My question is why?
>   I can't see what it is using the kernel lock to sync/protect against.

Metric buttload of users of ->d_parent in the filesystems.

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



kernel lock in dcache.c

2001-04-28 Thread Mark Hemment

Hi,

  d_move() in fs/dcache.c is checking the kernel lock is held
(switch_names() does the same, but is only called from d_move()).

  My question is why?
  I can't see what it is using the kernel lock to sync/protect against.

  Anyone out there know?

Thanks,
Mark

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



kernel lock in dcache.c

2001-04-28 Thread Mark Hemment

Hi,

  d_move() in fs/dcache.c is checking the kernel lock is held
(switch_names() does the same, but is only called from d_move()).

  My question is why?
  I can't see what it is using the kernel lock to sync/protect against.

  Anyone out there know?

Thanks,
Mark

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



Re: kernel lock in dcache.c

2001-04-28 Thread Alexander Viro



On Sat, 28 Apr 2001, Mark Hemment wrote:

 Hi,
 
   d_move() in fs/dcache.c is checking the kernel lock is held
 (switch_names() does the same, but is only called from d_move()).
 
   My question is why?
   I can't see what it is using the kernel lock to sync/protect against.

Metric buttload of users of -d_parent in the filesystems.

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