linux-kernel - Re: [GIT pull] timers/core for v6.13-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=wiX7=bqOEO06+BsO_25dHoa=KBWcNzLg=-rAKJ=dqKxYg@mail.gmail.com>
Date: Tue, 19 Nov 2024 16:33:45 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Thomas Gleixner <tglx@...utronix.de>, Christian Brauner <brauner@...nel.org>
Cc: linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [GIT pull] timers/core for v6.13-rc1

On Mon, 18 Nov 2024 at 11:22, Thomas Gleixner <tglx@...utronix.de> wrote:
>

>   - Core infrastructure for VFS multigrain timestamping
>
>     This is required to allow the kernel to use coarse grained time stamps
>     by default and switch to fine grained time stamps when inode attributes
>     are actively observed via getattr().
>
>     These changes have been provided to the VFS tree as well, so that the
>     VFS specific infrastructure could be built on top.

Bah. Except the vfs tree didn't take it as a shared branch, but
instead cherry-picked the commits and as a result they are duplicate
and caused a (trivial) merge conflict.

Oh well.

                 Linus