Received: by 2002:a05:6a10:2785:0:0:0:0 with SMTP id ia5csp3173312pxb; Tue, 12 Jan 2021 08:04:14 -0800 (PST) X-Google-Smtp-Source: ABdhPJyvGHMBa7shbRuof6Lf4fcclQyR+DuFjNzl/zI2z60kWTxqi3sd2B2jYjcnRrqXUMwCyAS/ X-Received: by 2002:a50:fc8b:: with SMTP id f11mr3989568edq.11.1610467453970; Tue, 12 Jan 2021 08:04:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610467453; cv=none; d=google.com; s=arc-20160816; b=FkODGF1XLf5nVuniwcOZOLog7tuMQgwCaavyrA4gX2mJ6RaQ5ft03soRRfjF6+HXoD vSeLTl7F/DoA6KVLWezqu2JjV/rIPxV0+otc6dbf3cNNgP0AfIrHZJ0hS/MXPMAbkNFs QLp0oFjSysvzbJi0hXXDdCzh1F8YHWZvqb/OzO0wzbIHlnTO7alJsbqNlOR55w7IaBiZ 9bqWwgNTh9GzUcpGkoVbWUXHuT90dgVH6YtP3+Medow0XoH/C83TbcCFq0cNjFOY6o5s rn9ruDMhQpe6eB98HYq6Ur+Grpr3PV13pHXRHxP570nF047FD5aHRTEle1cynHxT97X/ ruNg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:in-reply-to :subject:cc:to:from:message-id:date; bh=pX3ACiGMzzODGf76Ow/TR3AkXA8yR+jdk+8sTR0Klk0=; b=RodPEmgVzfxURktF2jfZkT3By+HuQYqpAqtdYVwpu5cCCUyjEOwjnd1kNfAAE6oZrE i2WLmUS+gJW1cWjUtEHDD0+Ygsg0yASmSbW4PZ0QpM+vSKt8dGCp83wCxI1Uwm4Hy3Sa MpWDVY3GYWsB3hCiGof9arhC14tHZAeJM3ocprA6NZYCAX8KRc7t5901hAVMdlhPAVoF VKcv2DdPCqlI32ZsOfY72MGD1QOnoYIsAPFI6UyRmpYvS5IHNSPKlwz226RBcS8woJ68 3quth+kAjtkPpk2cW7hPu+5EfEwUva8wYXDo1HryaTjqRnDKeHojMZAW9mlW0ufyVqPH 0e1w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id yw7si821685ejb.453.2021.01.12.08.03.50; Tue, 12 Jan 2021 08:04:13 -0800 (PST) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2405635AbhALQC5 (ORCPT + 99 others); Tue, 12 Jan 2021 11:02:57 -0500 Received: from mx2.suse.de ([195.135.220.15]:46562 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2405624AbhALQC4 (ORCPT ); Tue, 12 Jan 2021 11:02:56 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 2D2C3ABD6; Tue, 12 Jan 2021 16:02:15 +0000 (UTC) Date: Tue, 12 Jan 2021 17:02:15 +0100 Message-ID: From: Takashi Iwai To: Kalle Valo Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org, Luca Coelho Subject: Re: [PATCH 1/2] iwlwifi: dbg: Don't touch the tlv data In-Reply-To: <87turmrw9j.fsf@codeaurora.org> References: <20210112132449.22243-1-tiwai@suse.de> <20210112132449.22243-2-tiwai@suse.de> <87turmrw9j.fsf@codeaurora.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Tue, 12 Jan 2021 16:48:56 +0100, Kalle Valo wrote: > > Takashi Iwai writes: > > > The commit ba8f6f4ae254 ("iwlwifi: dbg: add dumping special device > > memory") added a termination of name string just to be sure, and this > > seems causing a regression, a GPF triggered at firmware loading. > > Basically we shouldn't modify the firmware data that may be provided > > as read-only. > > > > This patch drops the code that caused the regression and keep the tlv > > data as is. > > > > Fixes: ba8f6f4ae254 ("iwlwifi: dbg: add dumping special device memory") > > BugLink: https://bugzilla.suse.com/show_bug.cgi?id=1180344 > > BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=210733 > > Signed-off-by: Takashi Iwai > > I'm planning to queue this to v5.11. Should I add cc stable? Yes, it hits 5.10.y. > Luca, can I have your ack? It'd be great if this fix goes in quickly. BTW, I thought network people don't want to have Cc-to-stable in the patch, so I didn't put it by myself. Is this rule still valid? thanks, Takashi