linux-kernel - Re: linux-next: build failure after merge of the bluetooth tree

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 for Android: free password hash cracker in your pocket

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

Date:   Fri, 23 Jun 2023 14:28:06 +0200
From:   Alexander Mikhalitsyn <alexander@...alicyn.com>
To:     Christian Brauner <brauner@...nel.org>
Cc:     "Von Dentz, Luiz" <luiz.von.dentz@...el.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Marcel Holtmann <marcel@...tmann.org>,
        Johan Hedberg <johan.hedberg@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Jakub Kicinski <kuba@...nel.org>
Subject: Re: linux-next: build failure after merge of the bluetooth tree

On Fri, Jun 23, 2023 at 2:24 PM Christian Brauner <brauner@...nel.org> wrote:
>
> On Fri, Jun 23, 2023 at 11:23:57AM +0200, Alexander Mikhalitsyn wrote:
> > On Fri, Jun 23, 2023 at 10:34 AM Alexander Mikhalitsyn
> > <alexander@...alicyn.com> wrote:
> > >
> > > On Fri, Jun 23, 2023 at 12:28 AM Von Dentz, Luiz
> > > <luiz.von.dentz@...el.com> wrote:
> > > >
> > > > Hi Stephen, Alexander,
> > >
> > > Dear friends,
> > >
> > > >
> > > > Looks like we have a similar problem as to:
> > > >
> > > > https://lore.kernel.org/lkml/20230524081933.44dc8bea@kernel.org/
> > > >
> > > > That said for unix socket it was decided to not allow it to be build as module, which is something I don't think we are willing to do for bluetooth, so we have to find a way to get around pidfd_prepare, which seems to be called due to the use of scm_recv (it is also used by netlink btw).
> > >
> > > Ugh, yep. That's bad and we can't workaround it like we did for unix sockets.
> > >
> > > Originally, Christian had objections against exporting the
> > > pidfd_prepare function [1]
> > >
> > > [1] https://lore.kernel.org/all/20230523-flechten-ortsschild-e5724ecc4ed0@brauner/
> > >
> > > +cc Christian
> >
> > Idea. (-: We can introduce a new function like "scm_recv_light" that
>
> Seems fine to me.

Thanks, Christian!

Let's wait for Jakub's comment then :) Then I'll prepare and send a patch.

Kind regards,
Alex