Re: [PATCH] aio: propogate post-EIOCBQUEUED errors to completion event

> We don't try to resolve "conflicting" writes between ordinary mmap() and
> write(), so why should we be doing it for mmap and O_DIRECT?
> 
> mmap() is designed to violate the ordinary mutex locks for write(), so
> if a conflict arises, whether it be with O_DIRECT or ordinary writes
> then it is a case of "last writer wins".

but.. wouldn't an O_DIRECT *read* even cause this?


-
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: [PATCH] aio: propogate post-EIOCBQUEUED errors to completion event
  - From: Chris Mason <[email protected]>

References:
- [PATCH] aio: propogate post-EIOCBQUEUED errors to completion event
  - From: Zach Brown <[email protected]>
- RE: [PATCH] aio: propogate post-EIOCBQUEUED errors to completion event
  - From: "Ananiev, Leonid I" <[email protected]>
- Re: [PATCH] aio: propogate post-EIOCBQUEUED errors to completion event
  - From: Chris Mason <[email protected]>
- Re: [PATCH] aio: propogate post-EIOCBQUEUED errors to completion event
  - From: Benjamin LaHaise <[email protected]>
- Re: [PATCH] aio: propogate post-EIOCBQUEUED errors to completion event
  - From: Trond Myklebust <[email protected]>

Prev by Date: Re: [PATCH 1/5] sata_nv: Add CPB register info to error_handler output
Next by Date: Re: [PATCH] aio: propogate post-EIOCBQUEUED errors to completion event
Previous by thread: Re: [PATCH] aio: propogate post-EIOCBQUEUED errors to completion event
Next by thread: Re: [PATCH] aio: propogate post-EIOCBQUEUED errors to completion event
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]