From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 363DAEB64D7 for ; Fri, 23 Jun 2023 12:24:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230038AbjFWMYq (ORCPT ); Fri, 23 Jun 2023 08:24:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50580 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230117AbjFWMYo (ORCPT ); Fri, 23 Jun 2023 08:24:44 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4606483; Fri, 23 Jun 2023 05:24:43 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 95ECD61A43; Fri, 23 Jun 2023 12:24:42 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1BB5DC433C9; Fri, 23 Jun 2023 12:24:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1687523082; bh=9QiOf6qH4XnQzo7TTnAIieZs1DEpVgYd0lypn1ely/w=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=QSha6iZzPSfi13u534mCB7gH52LyolCeBRYwXLX8GscGHt37xr8ihXJRO6HQ3rFBx xLYuq5sSD948PvTEHqTi/FSfTf20uLepazpxKnkKuCXKw9J999Pv4gl3GnrbSQoFaE CuJ7aliSeSxNFqqk16S9Qc9uogdfyBWFM+QwXn/0qlrF5BtGqHV0XEdZVsJ9DTGD30 wS1jLrZWyMatcxGUr7McOixUFIPlT0ERuAM6vTTacnDxmoZpCxGczH5KKTQRxmwUEV YBrFM6OgyKkhUCum2ZpQR7H+chapbSx93+gfk+4OlIvmVMxqJ2vu9etMWtjJLVRy2m tq5qrm6t1eLzA== Date: Fri, 23 Jun 2023 14:24:37 +0200 From: Christian Brauner To: Alexander Mikhalitsyn Cc: "Von Dentz, Luiz" , Stephen Rothwell , Marcel Holtmann , Johan Hedberg , Linux Kernel Mailing List , Linux Next Mailing List , Jakub Kicinski Subject: Re: linux-next: build failure after merge of the bluetooth tree Message-ID: <20230623-baldigen-eisstadion-38bd00a856fb@brauner> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jun 23, 2023 at 11:23:57AM +0200, Alexander Mikhalitsyn wrote: > On Fri, Jun 23, 2023 at 10:34 AM Alexander Mikhalitsyn > wrote: > > > > On Fri, Jun 23, 2023 at 12:28 AM Von Dentz, Luiz > > 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.