Received: by 2002:a05:6358:c692:b0:131:369:b2a3 with SMTP id fe18csp3629037rwb; Sun, 30 Jul 2023 12:03:49 -0700 (PDT) X-Google-Smtp-Source: APBJJlHeCWF5O33Ej7h795HE6WNQlleYIFpVFog4L7IpBU+6nb6LPCedh9jVwQLGSN0gSGn+fP6u X-Received: by 2002:a17:90a:940d:b0:263:5376:b952 with SMTP id r13-20020a17090a940d00b002635376b952mr9550940pjo.9.1690743829577; Sun, 30 Jul 2023 12:03:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1690743829; cv=none; d=google.com; s=arc-20160816; b=ZaKArIMKfaQMNIc4U7lmVIWsxKOQOshcfkDAnuTmUbV1Stfd3D+4wziO7gbHeaiP6H 7O2Pul+4/w9IAS6ROR4pm9WmKhR7nx4wCMGydgLB1HihhRgB8RmxSBAAUoRH+pV+kSM7 T1P+3/0aBJts3NXjn1Ua5i7kCPXlln682EsBWPfLrN8TMaEJ25fyOzzayhEqYJLJu0tA c0mLHMP3x9qMRuuIgvt2xr9S1tEFwgyD61u94oRawZsVDTHWPe5ncoYFnYtW3S18fMJH yeL+zcooyziDOC+nyqXYrty/nfOc7AWkTQ+PTHWQlif2gYSTlYuO6mwZiXRFNz9h8bIJ vBCQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:date:content-id:mime-version:subject :cc:to:references:in-reply-to:from:organization:dkim-signature; bh=bI2QpHgEFPQgVStqd/H0LujPseNDGo/AgJRr8NE58KI=; fh=nTW11o5n6fBgvka4h4AK0rshRlbZUJ9nTJUGsvqwDcc=; b=s9W1ZqdGRiKl3nXxtdH2s5h7OrcpdsSWVWIK2CtJ1nKrnAv96qIeZUgqUYqKlbGbxN vW0mAcWHxF+EBJf10ZEx5uGTDIIoEG8xf2j28SrSzwZ9FoD9WPZHm9VKm1TydKc9n3i2 DBQqUtfXAqPubHdVwuevLACUXHjT1APL6061Q2fdLIblBiXpszaj55D7XROy/+XbjhG/ i2EjycsIaD1b/s7sTp3EcXfOFCIucmKXSpEXtMKRqlrjyxGyKzpy5BCIhZH7lOQOM9pH O+livxnpBgFfo6fd2sONbAYBlhc+SK5fTblugpSFMxD4qkPZwS37Zcvn/BVyf5zyO/pC Ddaw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=S+xuLnEd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id pc10-20020a17090b3b8a00b00267668f8be7si6533481pjb.64.2023.07.30.12.03.37; Sun, 30 Jul 2023 12:03:49 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=S+xuLnEd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229770AbjG3Rd6 (ORCPT + 99 others); Sun, 30 Jul 2023 13:33:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47040 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229469AbjG3Rd4 (ORCPT ); Sun, 30 Jul 2023 13:33:56 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D6E0390 for ; Sun, 30 Jul 2023 10:33:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1690738383; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=bI2QpHgEFPQgVStqd/H0LujPseNDGo/AgJRr8NE58KI=; b=S+xuLnEdNJo4a942wcr38DWaDHmIkCkgQz9DOCMbyA1mDsWIrc+uTndjVMG+BUjRuGofXW EmDVQ2wOcizE/gHUJ56Nr7Phnj9YLsJhi0Eyux/6qplqO90x9v0ZNbjIORwdXRZS5aOG/L yknV0XLgnrgm2S7UZBZiAEBOqom1SFA= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-125-3FQiQKGVOWy_qcO9uYKp8A-1; Sun, 30 Jul 2023 13:33:01 -0400 X-MC-Unique: 3FQiQKGVOWy_qcO9uYKp8A-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id A8A1B86F121; Sun, 30 Jul 2023 17:33:00 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.42.28.131]) by smtp.corp.redhat.com (Postfix) with ESMTP id E6A4A1415115; Sun, 30 Jul 2023 17:32:58 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <64c6672f580e3_11d0042944e@willemb.c.googlers.com.notmuch> References: <64c6672f580e3_11d0042944e@willemb.c.googlers.com.notmuch> <20230718160737.52c68c73@kernel.org> <000000000000881d0606004541d1@google.com> <0000000000001416bb06004ebf53@google.com> <792238.1690667367@warthog.procyon.org.uk> To: Willem de Bruijn Cc: dhowells@redhat.com, Jakub Kicinski , syzbot , bpf@vger.kernel.org, brauner@kernel.org, davem@davemloft.net, dsahern@kernel.org, edumazet@google.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, pabeni@redhat.com, syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk Subject: Re: Endless loop in udp with MSG_SPLICE_READ - Re: [syzbot] [fs?] INFO: task hung in pipe_release (4) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <810480.1690738378.1@warthog.procyon.org.uk> Date: Sun, 30 Jul 2023 18:32:58 +0100 Message-ID: <810481.1690738378@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Willem de Bruijn wrote: > The syzkaller repro runs in threaded mode, so syscalls should not be > interpreted in order. I think they are actually ordered. It's kind of weirdly done, though, flipping back and forth between threads and using futexes for synchronisation. David