freebsd
Exterrorize fuse_vnops.c
Next chunk of work on exterrorizing fuse code. Putting this on GitHub, because I divided changes into many commits - one commit per VOP. I will squash these commits before merging.
@asomers please take a look.
What's the state of userland support for this? Is ktrace still the only way to see the extended error codes?
Also, there are some lines over 80 characters wide.
These are all just ";" or ");" standing out and I thought it isn't a big deal. Should I fix all the GitHub Actions warnings listed in the "File changes" tab?
Also, there are some lines over 80 characters wide.
These are all just ";" or ");" standing out and I thought it isn't a big deal. Should I fix all the GitHub Actions warnings listed in the "File changes" tab?
I normally take a hard line about 80 characters and trailing white space. But I don't usually pay much attention to any other GitHub Actions style warnings.
Usuall the checker is pretty good. However this file has a number of variant style things that it flags that shouldn't be fixed since it makes some of the code not match and seems like too much churn. Line lengths have been moving toward 100 so if it's just a couple of characters over, I usually don't worry about it... but for this file, Alan wrote it, so a stricter adherence to the 80 rule seems warranted based of the match the existing style preference we have.
Clear as mud, eh? Tl;dr: do 80 cols, ignore return paren rule, but fix the rest.
Oh, I get it - I have 4-character tabs set in my editor. I now changed it to 8 according the style and see all the problems.