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 0055CC433F5 for ; Thu, 24 Mar 2022 08:55:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349062AbiCXI5Z (ORCPT ); Thu, 24 Mar 2022 04:57:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54612 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237920AbiCXI5V (ORCPT ); Thu, 24 Mar 2022 04:57:21 -0400 Received: from vulcan.natalenko.name (vulcan.natalenko.name [IPv6:2001:19f0:6c00:8846:5400:ff:fe0c:dfa0]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AEE4D9D074; Thu, 24 Mar 2022 01:55:49 -0700 (PDT) Received: from spock.localnet (unknown [83.148.33.151]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by vulcan.natalenko.name (Postfix) with ESMTPSA id BB8B5E491E9; Thu, 24 Mar 2022 09:55:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=natalenko.name; s=dkim-20170712; t=1648112146; 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: in-reply-to:in-reply-to:references:references; bh=S+woDWFZcPgqPY0chl6IjyANJVAaopdil00T5QCbF7E=; b=InO0yzyZU3QaeY3J8ths/cL9YOwpfDv9uIL616GmIlQRjsvz8ItHOgN2zT40/Y8FWsRSgP Kppy0V5Ft8HOz3rqo4NleRyvSAa1mMIR41RFSwE19LDUNek97TyGDRKmKZeaTpkkovO202 1p5wkp/jtBk8rE5/zx6jClPW0qttBkQ= From: Oleksandr Natalenko To: Linus Torvalds Cc: Halil Pasic , Christoph Hellwig , Marek Szyprowski , Robin Murphy , Toke =?ISO-8859-1?Q?H=F8iland=2DJ=F8rgensen?= , Kalle Valo , "David S. Miller" , Jakub Kicinski , Paolo Abeni , Olha Cherevyk , iommu , linux-wireless , Netdev , Linux Kernel Mailing List , Greg Kroah-Hartman , stable Subject: Re: [REGRESSION] Recent swiotlb DMA_FROM_DEVICE fixes break ath9k-based AP Date: Thu, 24 Mar 2022 09:55:44 +0100 Message-ID: <5806580.lOV4Wx5bFT@natalenko.name> In-Reply-To: References: <1812355.tdWV9SEqCh@natalenko.name> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello. On st=C5=99eda 23. b=C5=99ezna 2022 18:27:21 CET Linus Torvalds wrote: > On Wed, Mar 23, 2022 at 12:19 AM Oleksandr Natalenko > wrote: > > These commits appeared in v5.17 and v5.16.15, and both kernels are > > broken for me. I'm pretty confident these commits make the difference > > since I've built both v5.17 and v5.16.15 without them, and it fixed > > the issue. >=20 > Can you double-check (or just explicitly confirm if you already did > that test) that you need to revert *both* of those commits, and it's > the later "rework" fix that triggers it? I can confirm that if I revert aa6f8dcbab47 only, but leave ddbd89deb7d3 in= place, AP works. So, it seems that the latest "rework" triggers the issue = for me. Thanks. =2D-=20 Oleksandr Natalenko (post-factum)