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 C78BFC7EE23 for ; Fri, 24 Feb 2023 19:19:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229647AbjBXTTK (ORCPT ); Fri, 24 Feb 2023 14:19:10 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47240 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229458AbjBXTTJ (ORCPT ); Fri, 24 Feb 2023 14:19:09 -0500 Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3864A10C8 for ; Fri, 24 Feb 2023 11:19:08 -0800 (PST) Received: by mail-vs1-xe31.google.com with SMTP id o2so930834vss.8 for ; Fri, 24 Feb 2023 11:19:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uci-edu.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=beKhMtsCTaM5oM3Mze5dnKYHOlzx1cDOTU11CiVmTd8=; b=H3SEpbzsD7PRyycSfaIJTHQITmlJgkO7Io7xHoUfh6iiCZVz9xOrTv1LV5ScXsGbej M3JGKkz9ieE3+sdM+rX5Y49Yz5gd+cYX/v0ssXiXxWX4jF+LyGDKdjYOZyoHyZ7M6Hj8 Fjanq3xvT7H3csTgbOkTU6NCKQRA91J8J+5gTpS/aCv/4DTD22moW91JBqYzHOOB2pzm Ebke5bzH9WteMh+0aqP+q3oNr61B5MppI/LEvWcOeI2AvTZuq9P5IQTQW0boFKrEbLB7 7GVXbJurw3Hpq1Pu0Rii7SqEW3ZxpAErRkHGUYlomFpzjepes0z6uzV2TVE5ux+ASXT0 roaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=beKhMtsCTaM5oM3Mze5dnKYHOlzx1cDOTU11CiVmTd8=; b=8L73Wp3iDRQMVaSXSVkqJcRuzoUHUwbHMmZw8gn9nvf1rxm9sd5PF+7EQ1L3dQiehv XysHr/EsuxeAPLd4o0RBUu33aMEreMjSZldNFoqfHs/v/Ul+0+S6Wt+7a0ObHG8DE5xw Ah10bZNubfdqktcwI2YEsg1McL8P9DfG00tn76Irkj7ESIBwEG2N463gBdNTX1y0/d6V Ahclxj8mAe0LWwZX6SCxRf/rdtLAq4V1BLCR4Ejah6GfLhB5a0wvtpXpgFGJX7IFVGyz es0t953NxyfpwURPUBNBer/B/jgj3OUvdAOfAILL5zZYjHFxktdgGl09DtNPPE8DAR6t EVdA== X-Gm-Message-State: AO0yUKVidKI4bA5BGxEG/5tnV49qFxNGSL/qRb74yld0Py0eI6QFr+OB otkj4jQH/4Pmf3p8+AubR/uhy53QhTuw9u7GOumrRQ== X-Google-Smtp-Source: AK7set8lCRfbdrWNN0pLqcJuTWrdGmQzu4KmlBszfB3kfSMl8UPsYGuSJPDt8W5Ix1Vhgy16L8mKJ8WCEEKd5v8PayQ= X-Received: by 2002:a67:db0a:0:b0:414:2344:c353 with SMTP id z10-20020a67db0a000000b004142344c353mr3075359vsj.5.1677266347284; Fri, 24 Feb 2023 11:19:07 -0800 (PST) MIME-Version: 1.0 References: <87a614h62a.fsf@cloudflare.com> In-Reply-To: From: Hsin-Wei Hung Date: Fri, 24 Feb 2023 13:18:31 -0600 Message-ID: Subject: Re: A potential deadlock in sockhash map To: Jakub Sitnicki Cc: John Fastabend , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , netdev@vger.kernel.org, bpf@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hi, Just a quick update. I can still trigger the lockdep warning on bpf tree (5b7c4cabbb65). Thanks, Hsin-Wei On Fri, Feb 24, 2023 at 9:58 AM Hsin-Wei Hung wrote: > > Hi Jakub, > > Thanks for following up. Sorry that I did not receive the previous reply. > > The latest version I tested is 5.19 (3d7cb6b04c3f) and we can reproduce the > issue with the BPF PoC included. Since we modified Syzkaller, we do not > have a Syzkaller reproducer. > > I will follow John's suggestion to test the latest kernel and bpf > tree. I will follow > up if the issue still reproduces. > > Thanks, > Hsin-Wei > > > > > On Fri, Feb 24, 2023 at 8:51 AM Jakub Sitnicki wrote: > > > > Hi, > > > > On Mon, Feb 20, 2023 at 07:39 AM -06, Hsin-Wei Hung wrote: > > > I think my previous report got blocked since it contained HTML > > > subparts so I am sending it again. Our bpf runtime fuzzer (a > > > customized syzkaller) triggered a lockdep warning in the bpf subsystem > > > indicating a potential deadlock. We are able to trigger this bug on > > > v5.15.25 and v5.19. The following code is a BPF PoC, and the lockdep > > > warning is attached at the end. > > > > Not sure if you've seen John's reply to the previous report: > > > > https://urldefense.com/v3/__https://lore.kernel.org/all/63dddcc92fc31_6bb15208e9@john.notmuch/__;!!CzAuKJ42GuquVTTmVmPViYEvSg!PU-LFxMnx4b-GmTXGI0hYjBiq8vkwrFrlf_b0N5uzy8do5kPFiNcuZJbby-19TtOH2rJoY9UwOvzFArd$ > > > > Are you also fuzzing any newer kernel versions? Or was v5.19 the latest? > > > > Did syzkaller find a reproducer? > > > > Thanks, > > Jakub