<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in .gitignore</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>a23e1966932464e1c5226cb9ac4ce1d5fc10ba22 - Merge branch &apos;next&apos; into for-linus</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/fchmodat2/.gitignore#a23e1966932464e1c5226cb9ac4ce1d5fc10ba22</link>
        <description>Merge branch &apos;next&apos; into for-linusPrepare input updates for 6.11 merge window.

            List of files:
            /linux/tools/testing/selftests/fchmodat2/.gitignore</description>
        <pubDate>Mon, 15 Jul 2024 23:03:44 +0200</pubDate>
        <dc:creator>Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>6f47c7ae8c7afaf9ad291d39f0d3974f191a7946 - Merge tag &apos;v6.9&apos; into next</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/fchmodat2/.gitignore#6f47c7ae8c7afaf9ad291d39f0d3974f191a7946</link>
        <description>Merge tag &apos;v6.9&apos; into nextSync up with the mainline to bring in the new cleanup API.

            List of files:
            /linux/tools/testing/selftests/fchmodat2/.gitignore</description>
        <pubDate>Tue, 28 May 2024 06:37:18 +0200</pubDate>
        <dc:creator>Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>a1c613ae4c322ddd58d5a8539dbfba2a0380a8c0 - Merge drm/drm-next into drm-intel-gt-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/fchmodat2/.gitignore#a1c613ae4c322ddd58d5a8539dbfba2a0380a8c0</link>
        <description>Merge drm/drm-next into drm-intel-gt-nextWork that needs to land in drm-intel-gt-next depends on two patches onlypresent in drm-intel-next, absence of which is causing a merge conflict:  3b918f4f0c8b (&quot;drm/i915/pxp: Optimize GET_PARAM:PXP_STATUS&quot;)  ac765b7018f6 (&quot;drm/i915/pxp/mtl: intel_pxp_init_hw needs runtime-pm inside pm-complete&quot;)Signed-off-by: Tvrtko Ursulin &lt;tvrtko.ursulin@intel.com&gt;

            List of files:
            /linux/tools/testing/selftests/fchmodat2/.gitignore</description>
        <pubDate>Tue, 24 Oct 2023 10:50:22 +0200</pubDate>
        <dc:creator>Tvrtko Ursulin &lt;tvrtko.ursulin@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>a940daa52167e9db8ecce82213813b735a9d9f23 - Merge branch &apos;linus&apos; into smp/core</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/fchmodat2/.gitignore#a940daa52167e9db8ecce82213813b735a9d9f23</link>
        <description>Merge branch &apos;linus&apos; into smp/corePull in upstream to get the fixes so depending changes can be applied.

            List of files:
            /linux/tools/testing/selftests/fchmodat2/.gitignore</description>
        <pubDate>Tue, 17 Oct 2023 21:40:46 +0200</pubDate>
        <dc:creator>Thomas Gleixner &lt;tglx@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>57390019b68b83f96eb98f490367b9df1f2d77cb - Merge drm/drm-next into drm-misc-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/fchmodat2/.gitignore#57390019b68b83f96eb98f490367b9df1f2d77cb</link>
        <description>Merge drm/drm-next into drm-misc-nextUpdating drm-misc-next to the state of Linux v6.6-rc2.Signed-off-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;

            List of files:
            /linux/tools/testing/selftests/fchmodat2/.gitignore</description>
        <pubDate>Wed, 11 Oct 2023 09:50:59 +0200</pubDate>
        <dc:creator>Thomas Zimmermann &lt;tzimmermann@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>7d6904bf26b96ef087514cb7a8c50b62a4911c99 - Merge wireless into wireless-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/fchmodat2/.gitignore#7d6904bf26b96ef087514cb7a8c50b62a4911c99</link>
        <description>Merge wireless into wireless-nextResolve several conflicts, mostly between changes/fixes inwireless and the locking rework in wireless-next. One ofthe conflicts actually shows a bug in wireless that we&apos;llwant to fix separately.Signed-off-by: Johannes Berg &lt;johannes.berg@intel.com&gt;Signed-off-by: Kalle Valo &lt;kvalo@kernel.org&gt;

            List of files:
            /linux/tools/testing/selftests/fchmodat2/.gitignore</description>
        <pubDate>Thu, 05 Oct 2023 22:57:34 +0200</pubDate>
        <dc:creator>Johannes Berg &lt;johannes.berg@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>6f23fc47c1b2ac226704fb7294f43ed3b0965e51 - Merge tag &apos;v6.6-rc2&apos; into locking/core, to pick up fixes</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/fchmodat2/.gitignore#6f23fc47c1b2ac226704fb7294f43ed3b0965e51</link>
        <description>Merge tag &apos;v6.6-rc2&apos; into locking/core, to pick up fixesSigned-off-by: Ingo Molnar &lt;mingo@kernel.org&gt;

            List of files:
            /linux/tools/testing/selftests/fchmodat2/.gitignore</description>
        <pubDate>Mon, 18 Sep 2023 22:17:15 +0200</pubDate>
        <dc:creator>Ingo Molnar &lt;mingo@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>a3f9e4bc1ec9d8f1e352eb7c1cbaea3168246be7 - Merge drm/drm-next into drm-intel-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/fchmodat2/.gitignore#a3f9e4bc1ec9d8f1e352eb7c1cbaea3168246be7</link>
        <description>Merge drm/drm-next into drm-intel-nextSync to v6.6-rc1.Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;

            List of files:
            /linux/tools/testing/selftests/fchmodat2/.gitignore</description>
        <pubDate>Fri, 15 Sep 2023 10:23:38 +0200</pubDate>
        <dc:creator>Jani Nikula &lt;jani.nikula@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>c900529f3d9161bfde5cca0754f83b4d3c3e0220 - Merge drm/drm-fixes into drm-misc-fixes</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/fchmodat2/.gitignore#c900529f3d9161bfde5cca0754f83b4d3c3e0220</link>
        <description>Merge drm/drm-fixes into drm-misc-fixesForwarding to v6.6-rc1.Signed-off-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;

            List of files:
            /linux/tools/testing/selftests/fchmodat2/.gitignore</description>
        <pubDate>Tue, 12 Sep 2023 08:53:30 +0200</pubDate>
        <dc:creator>Thomas Zimmermann &lt;tzimmermann@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>475d4df82719225510625b4263baa1105665f4b3 - Merge tag &apos;v6.6-vfs.fchmodat2&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/fchmodat2/.gitignore#475d4df82719225510625b4263baa1105665f4b3</link>
        <description>Merge tag &apos;v6.6-vfs.fchmodat2&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfsPull fchmodat2 system call from Christian Brauner: &quot;This adds the fchmodat2() system call. It is a revised version of the  fchmodat() system call, adding a missing flag argument. Support for  both AT_SYMLINK_NOFOLLOW and AT_EMPTY_PATH are included.  Adding this system call revision has been a longstanding request but  so far has always fallen through the cracks. While the kernel  implementation of fchmodat() does not have a flag argument the libc  provided POSIX-compliant fchmodat(3) version does. Both glibc and musl  have to implement a workaround in order to support AT_SYMLINK_NOFOLLOW  (see [1] and [2]).  The workaround is brittle because it relies not just on O_PATH and  O_NOFOLLOW semantics and procfs magic links but also on our rather  inconsistent symlink semantics.  This gives userspace a proper fchmodat2() system call that libcs can  use to properly implement fchmodat(3) and allows them to get rid of  their hacks. In this case it will immediately benefit them as the  current workaround is already defunct because of aformentioned  inconsistencies.  In addition to AT_SYMLINK_NOFOLLOW, give userspace the ability to use  AT_EMPTY_PATH with fchmodat2(). This is already possible with  fchownat() so there&apos;s no reason to not also support it for  fchmodat2().  The implementation is simple and comes with selftests. Implementation  of the system call and wiring up the system call are done as separate  patches even though they could arguably be one patch. But in case  there are merge conflicts from other system call additions it can be  beneficial to have separate patches&quot;Link: https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/fchmodat.c;h=17eca54051ee28ba1ec3f9aed170a62630959143;hb=a492b1e5ef7ab50c6fdd4e4e9879ea5569ab0a6c#l35 [1]Link: https://git.musl-libc.org/cgit/musl/tree/src/stat/fchmodat.c?id=718f363bc2067b6487900eddc9180c84e7739f80#n28 [2]* tag &apos;v6.6-vfs.fchmodat2&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs:  selftests: fchmodat2: remove duplicate unneeded defines  fchmodat2: add support for AT_EMPTY_PATH  selftests: Add fchmodat2 selftest  arch: Register fchmodat2, usually as syscall 452  fs: Add fchmodat2()  Non-functional cleanup of a &quot;__user * filename&quot;

            List of files:
            /linux/tools/testing/selftests/fchmodat2/.gitignore</description>
        <pubDate>Mon, 28 Aug 2023 20:25:27 +0200</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>4859c257d295949c23f4074850a8c2ec31357abb - selftests: Add fchmodat2 selftest</title>
        <link>http://kernelsources.org:8080/source/history/linux/tools/testing/selftests/fchmodat2/.gitignore#4859c257d295949c23f4074850a8c2ec31357abb</link>
        <description>selftests: Add fchmodat2 selftestThe test marks as skipped if a syscall with the AT_SYMLINK_NOFOLLOW flagfails. This is because not all filesystems support changing the modebits of symlinks properly. These filesystems return an error but changethe mode bits:newfstatat(4, &quot;regfile&quot;, {st_mode=S_IFREG|0640, st_size=0, ...}, AT_SYMLINK_NOFOLLOW) = 0newfstatat(4, &quot;symlink&quot;, {st_mode=S_IFLNK|0777, st_size=7, ...}, AT_SYMLINK_NOFOLLOW) = 0syscall_0x1c3(0x4, 0x55fa1f244396, 0x180, 0x100, 0x55fa1f24438e, 0x34) = -1 EOPNOTSUPP (Operation not supported)newfstatat(4, &quot;regfile&quot;, {st_mode=S_IFREG|0640, st_size=0, ...}, AT_SYMLINK_NOFOLLOW) = 0This happens with btrfs and xfs: $ tools/testing/selftests/fchmodat2/fchmodat2_test TAP version 13 1..1 ok 1 # SKIP fchmodat2(symlink) # Totals: pass:0 fail:0 xfail:0 xpass:0 skip:1 error:0 $ stat /tmp/ksft-fchmodat2.*/symlink   File: /tmp/ksft-fchmodat2.3NCqlE/symlink -&gt; regfile   Size: 7               Blocks: 0          IO Block: 4096   symbolic link Device: 7,0     Inode: 133         Links: 1 Access: (0600/lrw-------)  Uid: (    0/    root)   Gid: (    0/    root)Signed-off-by: Alexey Gladkov &lt;legion@kernel.org&gt;Message-Id: &lt;4532a04a870ff589ba62ceeacf76f0bd81b9ba01.1689092120.git.legion@kernel.org&gt;Signed-off-by: Christian Brauner &lt;brauner@kernel.org&gt;

            List of files:
            /linux/tools/testing/selftests/fchmodat2/.gitignore</description>
        <pubDate>Tue, 11 Jul 2023 18:16:07 +0200</pubDate>
        <dc:creator>Alexey Gladkov &lt;legion@kernel.org&gt;</dc:creator>
    </item>
</channel>
</rss>
