4 Aug
2010
4 Aug
'10
10:46 p.m.
On Wed, 2010-08-04 at 14:19 +0100, Chris Wilson wrote:
This is consistent with trying to access a filename that not exist within a directory which is a good analogy here. The main reason for the change is that it is easy to confuse the error code of EBADF as an performing an ioctl on an invalid file descriptor (rather than an unknown object).
Have you verified no userspace relies on this return value? since this technically an ABI change.
From what I can see probably only libdrm tests care.
Dave.