<feed xmlns='http://www.w3.org/2005/Atom'>
<title>glibc/io, branch vdso</title>
<subtitle>Fork of glibc for development</subtitle>
<id>https://git.zx2c4.com/glibc/atom/io?h=vdso</id>
<link rel='self' href='https://git.zx2c4.com/glibc/atom/io?h=vdso'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/'/>
<updated>2024-09-09T07:51:50Z</updated>
<entry>
<title>io: Add FUSE-based test for fchmod</title>
<updated>2024-09-09T07:51:50Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2024-08-22T09:02:51Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=43669fcf7315f494bbbc2c040cedeb0fa8416a5f'/>
<id>urn:sha1:43669fcf7315f494bbbc2c040cedeb0fa8416a5f</id>
<content type='text'>
Test all mode arguments, and that extra bits are ignored
as required by POSIX.

Reviewed-by: DJ Delorie &lt;dj@redhat.com&gt;
</content>
</entry>
<entry>
<title>io: Add tst-lstat-nofollow, tst-lstat-nofollow-time64</title>
<updated>2024-09-09T07:14:22Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2024-08-29T09:06:08Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=f4ae345810942db891bddf9b482c72b3a120c3b2'/>
<id>urn:sha1:f4ae345810942db891bddf9b482c72b3a120c3b2</id>
<content type='text'>
They verify that lstat, lstat64 do not follow symbolic links.

Reviewed-by: DJ Delorie &lt;dj@redhat.com&gt;
</content>
</entry>
<entry>
<title>io: Fix destructive nature of tst-fchmod-errors</title>
<updated>2024-08-30T20:30:05Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2024-08-30T20:07:12Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=3844cdc33093dbe1e33ddb831eada9bdb4a482b9'/>
<id>urn:sha1:3844cdc33093dbe1e33ddb831eada9bdb4a482b9</id>
<content type='text'>
We must not change the permissions of /dev/null if running
as root.

Reviewed-by: Carlos O'Donell &lt;carlos@redhat.com&gt;
</content>
</entry>
<entry>
<title>io: Add error tests for fchmod</title>
<updated>2024-08-30T19:12:01Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2024-08-30T18:37:18Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=424d97be50488beb6196c0ff0bc3dfeb87b4281c'/>
<id>urn:sha1:424d97be50488beb6196c0ff0bc3dfeb87b4281c</id>
<content type='text'>
On Linux most descriptors that do not correspond to file system
entities (such as anonymous pipes and sockets) have file permissions
that can be changed.  While it is possible to create a custom file
system that returns (say) EINVAL for an fchmod attempt, testing this
does not appear to be useful.

Reviewed-by: Carlos O'Donell &lt;carlos@redhat.com&gt;
</content>
</entry>
<entry>
<title>Test mkdirat use of mode argument</title>
<updated>2024-08-22T11:25:14Z</updated>
<author>
<name>Joseph Myers</name>
<email>josmyers@redhat.com</email>
</author>
<published>2024-08-22T11:25:14Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=55cd51d971b84fbb2cc0fe8140cc8581f98582c7'/>
<id>urn:sha1:55cd51d971b84fbb2cc0fe8140cc8581f98582c7</id>
<content type='text'>
The test io/tst-mkdirat doesn't verify the permissions on the created
directory (thus, doesn't verify at all anything about how mkdirat uses
the mode argument).  Add checks of this to the existing test.

Tested for x86_64.
</content>
</entry>
<entry>
<title>support: Use macros for *stat wrappers</title>
<updated>2024-08-16T14:05:20Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2024-08-16T14:05:20Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=e7c14e542d8d858b824b5df4f4e3dc93695e6171'/>
<id>urn:sha1:e7c14e542d8d858b824b5df4f4e3dc93695e6171</id>
<content type='text'>
Macros will automatically use the correct types, without
having to fiddle with internal glibc macros.  It's also
impossible to get the types wrong due to aliasing because
support_check_stat_fd and support_check_stat_path do not
depend on the struct stat* types.

The changes reveal some inconsistencies in tests.

Reviewed-by: Adhemerval Zanella &lt;adhemerval.zanella@linaro.org&gt;
</content>
</entry>
<entry>
<title>io: Use struct statx and xstatx in tests</title>
<updated>2024-08-16T14:05:20Z</updated>
<author>
<name>Florian Weimer</name>
<email>fweimer@redhat.com</email>
</author>
<published>2024-08-16T14:05:20Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=bf2927484152e12996af60ea439cf94b66fcd81d'/>
<id>urn:sha1:bf2927484152e12996af60ea439cf94b66fcd81d</id>
<content type='text'>
This avoids the need to define struct_statx to an appropriate
struct stat type variant because struct statx does not change
based on time/file offset flags.

Reviewed-by: Adhemerval Zanella &lt;adhemerval.zanella@linaro.org&gt;
</content>
</entry>
<entry>
<title>Add STATX_SUBVOL from Linux 6.10 to bits/statx-generic.h</title>
<updated>2024-07-30T11:48:51Z</updated>
<author>
<name>Adhemerval Zanella</name>
<email>adhemerval.zanella@linaro.org</email>
</author>
<published>2024-07-16T17:08:48Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=bbb6a742c88b4a37c5410eceefbc9c94df815075'/>
<id>urn:sha1:bbb6a742c88b4a37c5410eceefbc9c94df815075</id>
<content type='text'>
Tested for aarch64-linux-gnu.
Reviewed-by: Florian Weimer &lt;fweimer@redhat.com&gt;
</content>
</entry>
<entry>
<title>debug: Fix clang open fortify wrapper (BZ 31927)</title>
<updated>2024-07-02T13:19:44Z</updated>
<author>
<name>Adhemerval Zanella</name>
<email>adhemerval.zanella@linaro.org</email>
</author>
<published>2024-06-28T19:20:15Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=9f80d8134a15235732586e238ac28cea459fb60b'/>
<id>urn:sha1:9f80d8134a15235732586e238ac28cea459fb60b</id>
<content type='text'>
The clang open fortify wrapper from 4228baef1a94e8bde84ad74 added
a restriction where open with 3 arguments where flags do not
contain O_CREAT or O_TMPFILE are handled as invalid.  They are
not invalid, since the third argument is ignored, and the gcc
wrapper also allows it.

Checked x86_64-linux-gnu and with a yocto build for some affected
packages.
Tested-by: “Khem Raj &lt;raj.khen@gmail.com&gt;”
</content>
</entry>
<entry>
<title>debug: Fix clang open fortify wrapper (BZ 31927)</title>
<updated>2024-06-27T16:32:48Z</updated>
<author>
<name>Adhemerval Zanella</name>
<email>adhemerval.zanella@linaro.org</email>
</author>
<published>2024-06-25T14:57:15Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/glibc/commit/?id=4228baef1a94e8bde84ad74f2e0358120a2bcac7'/>
<id>urn:sha1:4228baef1a94e8bde84ad74f2e0358120a2bcac7</id>
<content type='text'>
The fcntl.h fortify wrapper for clang added by 86889e22db329abac61
missed the __fortify_clang_overload_arg and and also added the
mode argument for the __fortify_function_error_function function,
which leads clang to be able to correct resolve which overloaded
function it should emit.

Checked on x86_64-linux-gnu.

Reported-by: Khem Raj &lt;raj.khem@gmail.com&gt;
Tested-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
</feed>
