On Thu, 2005-04-07 at 14:22 +0100, Christoph Hellwig wrote: > Do we really need the sdev_lock pointer? There's just a single place > where we're using it and the code would be much more clear if it had just > one name. Humour me for a while. I don't believe we have any way the lock can be used after calling queue free, but nulling the sdev_lock pointer will surely catch them. If nothing turns up after a few kernel revisions, feel free to kill it. James - 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/
- Follow-Ups:
- Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- From: Jens Axboe <[email protected]>
- Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- References:
- Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- From: Chris Rankin <[email protected]>
- Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- From: Jens Axboe <[email protected]>
- Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- From: James Bottomley <[email protected]>
- Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- From: Jens Axboe <[email protected]>
- Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- From: James Bottomley <[email protected]>
- Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- From: Jens Axboe <[email protected]>
- Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- From: James Bottomley <[email protected]>
- Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- From: Jens Axboe <[email protected]>
- Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- From: James Bottomley <[email protected]>
- Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- From: Christoph Hellwig <[email protected]>
- Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- Prev by Date: Re: non-free firmware in kernel modules, aggregation and unclear copyright notice.
- Next by Date: Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- Previous by thread: Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- Next by thread: Re: [OOPS] 2.6.11 - NMI lockup with CFQ scheduler
- Index(es):