Re: [RFC] Badness in __mutex_unlock_slowpath with XFS stress tests

On Thu, Mar 09, 2006 at 01:24:38PM +0530, Suzuki wrote:
> 
> Missed out linux-aio & linux-fs-devel lists. Forwarding.
> 
> Comments ?

I've seen this too.  The problem is that __generic_file_aio_read can return
with or without the i_mutex locked in the direct I/O case for filesystems
that set DIO_OWN_LOCKING.  It's a nasty one and I haven't found a better solution
than copying lots of code from filemap.c into xfs.

-
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: [RFC] Badness in __mutex_unlock_slowpath with XFS stress tests
  - From: Nathan Scott <[email protected]>

References:
- [RFC] Badness in __mutex_unlock_slowpath with XFS stress tests
  - From: Suzuki <[email protected]>

Prev by Date: Re: [PATCH] Document Linux's memory barriers [try #2]
Next by Date: Re: 2.6.16-rc5-mm3 -- BUG: sleeping function called from invalid context at include/linux/rwsem.h:43 in_atomic():0, irqs_disabled():1
Previous by thread: [RFC] Badness in __mutex_unlock_slowpath with XFS stress tests
Next by thread: Re: [RFC] Badness in __mutex_unlock_slowpath with XFS stress tests
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]