This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: pwritev2 regression test for invalid flags
On 21/06/2017 10:08, Florian Weimer wrote:
> On 06/21/2017 03:06 PM, Adhemerval Zanella wrote:
>>
>>
>> On 21/06/2017 08:45, Florian Weimer wrote:
>>> On 06/20/2017 10:53 PM, Stephen Bates wrote:
>>>>>
>>>>>> I've already sent this patch to Al twice (including a stable tag),
>>>>>> but it didn't seem to make it anywhere.
>>>>
>>>> Does anyone have ideas how we move this along? This is the missing link in allowing applications to request IO polling…
>>>
>>> Is this still an issue with the upstream kernel?
>>>
>>> As far as I can tell, Greg Kroah-Hartman queued the fix for 4.9 and
>>> 4.11, and the fix is in mainline, too:
>>>
>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=20223f0f39ea9d31ece08f04ac79f8c4e8d98246
>>
>> Would it be acceptable to add an issue that stress this issue on glibc?
>
> Sure, except that it is difficult to pull a guaranteed-to-be-invalid
> combination of flags out of thin air. Even -1 might eventually cease to
> work.
>
> Thanks,
> Florian
>
Yes, we will need to update the testcase in case of newer flags additions.
But since the flags are currently defined within GLIBC not pulling from
kernel header I think we will have more control over it.