Fix handling of ITER_IOVEC

[rafaelroquetto]

In certain kernel versions, ITER_IOVEC can be 0, which causes the following condition to be wrongly evaluated:

if ((ctx.iter_type & ITER_IOVEC) != ITER_IOVEC) {
/* ... */
}

Instead we treat ITER_IOVEC as a proper value instead of performing bitwise comparisons.

Tested on kernels

• 5.10
• 6.1
• 6.4
• 6.6
• 6.10

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.83%. Comparing base (81e027f) to head (9552072).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1090      +/-   ##
==========================================
+ Coverage   73.09%   73.83%   +0.74%     
==========================================
  Files         172      172              
  Lines       13066    13066              
==========================================
+ Hits         9550     9647      +97     
+ Misses       2968     2872      -96     
+ Partials      548      547       -1     

Flag	Coverage Δ
integration-test	51.01% <ø> (+0.16%)	⬆️
k8s-integration-test	52.92% <ø> (+0.03%)	⬆️
oats-test	33.96% <ø> (+0.51%)	⬆️
unittests	45.66% <ø> (+0.03%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[grcevski]

LGTM! Nice!