Hi Peter, On 3/29/21 11:51 PM, Peter Xu wrote: > On Thu, Mar 25, 2021 at 10:32:20PM +0100, Alejandro Colomar (man-pages) wrote: >>>>> +.TP >>>>> +.B ENOENT >>>>> +The range specified in >>>>> +.I range >>>>> +is not valid. >>>> >>>> I'm not sure how this is different from the wording above in EINVAL. An >>>> "otherwise invalid range" was already giving EINVAL? >>> >>> This can be returned when vma is not found (mwriteprotect_range()): >>> >>> err = -ENOENT; >>> dst_vma = find_dst_vma(dst_mm, start, len); >>> >>> if (!dst_vma) >>> goto out_unlock; >>> >>> I think maybe I could simply remove this entry, because from an user app >>> developer pov I'd only be interested in specific error that I'd be able to >>> detect and (even better) recover from. For such error I'd say there's not much >>> to do besides failing the app. >> >> If there's any possibility that the error can happen, it should be >> documented, even if it's to say "Fatal error; abort!". Just try to explain >> the causes and how to avoid causing them and/or possibly what to do when >> they happen (abort?). > > Okay. Would you mind me keeping my original wording? Because IMHO that > exactly does what you said as "trying to explain the causes" and so on: > > .B ENOENT > The range specified in > .I range > is not valid. > For example, the virtual address does not exist, > or not registered with userfaultfd write-protect mode. > > It's indeed slightly duplicated with EINVAL, but if you don't agree with the > wording meanwhile if you don't agree on overlapping of the errors, then what I > need is not reworking this patchset, but proposing a kernel patch to change the > error retval to make them match. I am not against proposing a kernel patch, but > I just don't see it extremely necessary. > > For my own experience on working with the kernel, the return value sometimes is > not that strict - say, it's hard to control every single bit of the possible > return code of a syscall/ioctl to reflect everything matching the document. We > should always try to do it accurate but it seems not easy to me. It's also > hard to write up the document that 100% matching the kernel code, because at > least that'll require a full-path workthrough of every single piece of kernel > code that the syscall/ioctl has called, so as to collect all the errors, then > summarize their meanings. That could be a lot of work. Yes, That's fine. I was only curious about the overlap, but if they do overlap, that's it. >>>>> +For example, the virtual address does not exist, >>>>> +or not registered with userfaultfd write-protect mode. >>>>> +.TP >>>>> +.B EFAULT >>>>> +Encountered a generic fault during processing. >>>> >>>> What is a "generic fault"? >>> >>> For example when the user copy failed due to some reason. See >>> userfaultfd_writeprotect(): >>> >>> if (copy_from_user(&uffdio_wp, user_uffdio_wp, >>> sizeof(struct uffdio_writeprotect))) >>> return -EFAULT; >>> >>> But I didn't check other places, generally I'd return -EFAULT if I can't find a >>> proper other replacement which has a clearer meaning. >>> >>> I don't think this is really helpful to user app too because no user app would >>> start to read this -EFAULT to do anything useful.. how about I drop it too if >>> you think the description is confusing? >> >> Same as above. > > Above copy_from_user() is the only place that could trigger -EFAULT so far I > can find. So either I can change above into: > > .TP > .B EFAULT > Failure on copying ioctl parameters into the kernel. > > Would you think it okay (before I repost)? I'd still prefer my original > wording because I bet 90% user developer may not even know what does it mean > when the kernel cannot copy the user parameter, and what he/she can do with > it.. However if you think it's proper I'll use it. Okay, I'll take your original words. Maybe all this "extra" info could go into the commit message. I'll wait for your resend with the a-b and the minor changes :-) Thanks, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/
