Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp4323555rwb; Mon, 21 Nov 2022 06:24:25 -0800 (PST) X-Google-Smtp-Source: AA0mqf7orphSNjN2PNF5/BRJZpiTHjiBwVRv84ucHVQToZk746crakh33yxAwevPiGwRjcl3JNzE X-Received: by 2002:a05:6402:388e:b0:468:fb0d:2d8b with SMTP id fd14-20020a056402388e00b00468fb0d2d8bmr14810615edb.124.1669040664798; Mon, 21 Nov 2022 06:24:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1669040664; cv=none; d=google.com; s=arc-20160816; b=V2Ek5903OLVCMqBiNFepP+K1ONiZdAvqKDZnrKSzPiXZBl3M2rsVza23a2I4aWZGLd Ojn+1aqIwssse7sTMlGBzVo0LxJ6ThQF/aZoMMgkktM+73If8onr6G9ppd2t6Zpbo9+5 1PNFWu42Jtl4TvxIQ/2GI3EQ9xjbuXM/w+6BtNep156caLk/WZBMttH36Kq3eGZIQJef 2ZWrZ29b/CUnre5mfwKHWdJmZxyKwmVvjhlbtiGkiJzpxjmXOSekIX5ZQsxCBQKdw2ye ZNaMCQ5GrxtRhtkMchx+r9wJllh80Z2dTt4iSXuEDAHtENWCuiBpNCn4oo23KYx080HN XgOg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=kv3DFPK60Zt0kQKX09txPuy6ctuc3jatg8rhDf4HcIA=; b=iVMKKXUQySLV6fu3JumXsxjPHv7rTlVIv0EsgiwA9kP6EIo6+0DpVFqiWQB+ZI6tA0 FcWBfQDOH9j4PYrnTO+pMvtS0w+7mBp6CUH771KGhfMChKBbLZ60s8D/xpH37njJYBBl 5B8eDcD+Yl4entv6lgit5Tb479a8miQspOru31BZjKvCazkO4Og8Kx6zitW0UjgRGgEL X8Th44Hd3Tc3YDUqrcy7DRoO80fvsfOW9RrSiCO2jhP7uopifmnia9T5Pbm3N5xUxiZX gYd7FfkW/3C+T6MulcQZK/G0xEz5r7vQuTVeeWB7czpiJo15b2G1O2qtvFFZsnjT6iXE nDdg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=fND9JFM9; 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 g39-20020a056402322700b0045beaf03ddesi8872951eda.411.2022.11.21.06.23.56; Mon, 21 Nov 2022 06:24:24 -0800 (PST) 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=fND9JFM9; 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 S230497AbiKUNgd (ORCPT + 91 others); Mon, 21 Nov 2022 08:36:33 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41762 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230481AbiKUNg1 (ORCPT ); Mon, 21 Nov 2022 08:36:27 -0500 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 33BD9C2860 for ; Mon, 21 Nov 2022 05:35:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1669037726; 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: content-transfer-encoding:content-transfer-encoding; bh=kv3DFPK60Zt0kQKX09txPuy6ctuc3jatg8rhDf4HcIA=; b=fND9JFM9bIWk34xKMRNl9RwHdoOOgNsjO3OyM0Gb3CP+sNsJukpXSpp6+i+Dcek7kY8NrY nqHmKieCBiLP26LOx+Ukug4UxqNBfkPperXdWoQL5K/e997TZu/gIgseyKUr8HgGYwweAT jhbC0xDZiJf5OrCLQiLV9uaAcyS+3X8= 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-651-P1zce99uPti9aGvqoLm26g-1; Mon, 21 Nov 2022 08:35:23 -0500 X-MC-Unique: P1zce99uPti9aGvqoLm26g-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id E89FA887400; Mon, 21 Nov 2022 13:35:22 +0000 (UTC) Received: from bcodding.csb (unknown [10.22.50.7]) by smtp.corp.redhat.com (Postfix) with ESMTP id B230117585; Mon, 21 Nov 2022 13:35:22 +0000 (UTC) Received: by bcodding.csb (Postfix, from userid 24008) id 33D9010C30E3; Mon, 21 Nov 2022 08:35:19 -0500 (EST) From: Benjamin Coddington To: netdev@vger.kernel.org Cc: linux-kernel@vger.kernel.org Subject: [PATCH v1 0/3] Stop corrupting socket's task_frag Date: Mon, 21 Nov 2022 08:35:16 -0500 Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 3.1 on 10.11.54.5 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_H2,SPF_HELO_NONE,SPF_NONE autolearn=unavailable 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 The networking code uses flags in sk_allocation to determine if it can use current->task_frag, however in-kernel users of sockets may stop setting sk_allocation when they convert to the preferred memalloc_nofs_save/restore, as SUNRPC has done in commit a1231fda7e94 ("SUNRPC: Set memalloc_nofs_save() on all rpciod/xprtiod jobs"). This will cause corruption in current->task_frag when recursing into the network layer for those subsystems during page fault or reclaim. The corruption is difficult to diagnose because stack traces may not contain the offending subsystem at all. The corruption is unlikely to show up in testing because it requires memory pressure, and so subsystems that convert to memalloc_nofs_save/restore are likely to continue to run into this issue. Previous reports and proposed fixes: https://lore.kernel.org/netdev/96a18bd00cbc6cb554603cc0d6ef1c551965b078.1663762494.git.gnault@redhat.com/ https://lore.kernel.org/netdev/b4d8cb09c913d3e34f853736f3f5628abfd7f4b6.1656699567.git.gnault@redhat.com/ https://lore.kernel.org/linux-nfs/de6d99321d1dcaa2ad456b92b3680aa77c07a747.1665401788.git.gnault@redhat.com/ Guilluame Nault has done all of the hard work tracking this problem down and finding the best fix for this issue. I'm just taking a turn posting another fix. Benjamin Coddington (2): Treewide: Stop corrupting socket's task_frag net: simplify sk_page_frag Guillaume Nault (1): net: Introduce sk_use_task_frag in struct sock. drivers/block/drbd/drbd_receiver.c | 3 +++ drivers/block/nbd.c | 1 + drivers/nvme/host/tcp.c | 1 + drivers/scsi/iscsi_tcp.c | 1 + drivers/usb/usbip/usbip_common.c | 1 + fs/afs/rxrpc.c | 1 + fs/cifs/connect.c | 1 + fs/dlm/lowcomms.c | 2 ++ fs/ocfs2/cluster/tcp.c | 1 + include/net/sock.h | 10 ++++++---- net/9p/trans_fd.c | 1 + net/ceph/messenger.c | 1 + net/core/sock.c | 1 + net/sunrpc/xprtsock.c | 3 +++ 14 files changed, 24 insertions(+), 4 deletions(-) -- 2.31.1