linux-kernel - Re: [GIT PULL] vfs mount

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: <20240914123304.172831bd@canb.auug.org.au>
Date: Sat, 14 Sep 2024 12:33:04 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Christian Brauner <brauner@...nel.org>, linux-fsdevel@...r.kernel.org,
 linux-kernel@...r.kernel.org, Al Viro  <viro@...iv.linux.org.uk>
Subject: Re: [GIT PULL] vfs mount

Hi Linus,

On Fri, 13 Sep 2024 16:41:58 +0200 Christian Brauner <brauner@...nel.org> wrote:
>
> (1) linux-next: build failure after merge of the bpf-next tree
>     https://lore.kernel.org/r/20240913133240.066ae790@canb.auug.org.au
> 
>     The reported merge conflict isn't really with bpf-next but with the
>     series to convert to fd_file() accessors for the changed struct fd
>     representation.
> 
>     The patch you need to fix this however is correct in that draft. But
>     honestly, it's pretty easy for you to figure out on your own anyway.

Except Al Viro told me an earlier time we had this conflict (the commit
the did the convert to fd_file() was removed form linux-next for a while)
that !fd_file(f) should (could)? be replaced by fd_empty(f) - but that
may be done later.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped