Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1361959
| From | Christoph Hellwig <hch@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [patch] direct-io: propagate -ENOSPC errors |
| Date | 2016-03-21 17:10 +0100 |
| Message-ID | <rfaz0-86k-7@gated-at.bofh.it> (permalink) |
| References | <rcI4a-P4-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Mar 14, 2016 at 05:10:00PM -0400, Jeff Moyer wrote: > dio_bio_complete turns all errors into -EIO. This is historical, > since you used to only get 1 bit precision for errors (BIO_UPTODATE). > Now that we get actual error codes, we can return the appropriate > code to userspace. File systems seem to only propagate either EIO > or ENOSPC, so I've followed suit in this patch. Do we? Just propagating some errors defintively seems odd. Even if we do we should have a central helper doing that mapping instead of opencoding it in various places.
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [patch] direct-io: propagate -ENOSPC errors Christoph Hellwig <hch@infradead.org> - 2016-03-21 17:10 +0100 Re: [patch] direct-io: propagate -ENOSPC errors Jeff Moyer <jmoyer@redhat.com> - 2016-03-21 21:30 +0100
csiph-web