Re: [PATCH][RFC] sigurg/sigio cleanup for 2.5.31

From: James Morris (jmorris@intercode.com.au)
Date: Fri Aug 16 2002 - 08:07:22 EST

Next message: Ingo Molnar: "Re: [patch] user-vm-unlock-2.5.31-A2"
Previous message: Christoph Hellwig: "Re: [PATCH] simplify b_inode usage"
Next in thread: kuznet@ms2.inr.ac.ru: "Re: [PATCH][RFC] sigurg/sigio cleanup for 2.5.31"
Reply: kuznet@ms2.inr.ac.ru: "Re: [PATCH][RFC] sigurg/sigio cleanup for 2.5.31"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Fri, 16 Aug 2002 kuznet@ms2.inr.ac.ru wrote:

> I do not know what forced you to use BKL.

All existing paths which write to the pid/uid/euid fields are protected by
the BKL (except for the futex code, which doesn't need it). None of
these, or the new paths which grab the BKL, are performance critical, as
they're ioctl() or fcntl() handlers.

> But I daresay this is deadlock:

Yep.

- James

-- James Morris <jmorris@intercode.com.au>

- 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/

Next message: Ingo Molnar: "Re: [patch] user-vm-unlock-2.5.31-A2"
Previous message: Christoph Hellwig: "Re: [PATCH] simplify b_inode usage"
Next in thread: kuznet@ms2.inr.ac.ru: "Re: [PATCH][RFC] sigurg/sigio cleanup for 2.5.31"
Reply: kuznet@ms2.inr.ac.ru: "Re: [PATCH][RFC] sigurg/sigio cleanup for 2.5.31"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Aug 23 2002 - 22:00:12 EST