Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1697480

nowait aio return value

From Jason Baron <jbaron@akamai.com>
Newsgroups linux.kernel
Subject nowait aio return value
Date 2017-07-26 20:50 +0200
Message-ID <u7zxD-3Wx-11@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View raw


Hi,

In testing nowait aio on ext4, I found that when appending to a file
the return value is EAGAIN/EWOULDBLOCK, because as mentioned in the 
commit this will potentially trigger an allocation. However, the EAGAIN, 
seems somewhat misleading to me, in that if I continuously try the 
write, it will never succeed.

The relevant commit is:
728fbc0 ext4: nowait aio support

As you can see there, failure to get the inode lock is treated as
EAGAIN, which seems more appropriate to me, as its very likely
to succeed on subsequent calls.

Perhaps, it could be switched to -EINVAL, or something else?

Thanks,

-Jason

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

nowait aio return value Jason Baron <jbaron@akamai.com> - 2017-07-26 20:50 +0200
  Re: nowait aio return value Goldwyn Rodrigues <rgoldwyn@suse.de> - 2017-07-26 23:20 +0200

csiph-web