From: Kalle Valo <kvalo@codeaurora.org>
To: Michal Kubecek <mkubecek@suse.cz>
Cc: linux-wireless@vger.kernel.org,
Mordechay Goodstein <mordechay.goodstein@intel.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Takashi Iwai <tiwai@suse.de>,
Arjen de Korte <suse+build@de-korte.org>,
Luca Coelho <luciano.coelho@intel.com>
Subject: Re: regression in iwlwifi: page fault in iwl_dbg_tlv_alloc_region() (commit ba8f6f4ae254)
Date: Tue, 12 Jan 2021 13:33:14 +0200 [thread overview]
Message-ID: <87v9c2qtj9.fsf@tynnyri.adurom.net> (raw)
In-Reply-To: <20201228115814.GA5880@lion.mk-sys.cz> (Michal Kubecek's message of "Mon, 28 Dec 2020 12:58:14 +0100")
(adding luca)
Michal Kubecek <mkubecek@suse.cz> writes:
> FYI, there is a regression in iwlwifi driver caused by commit
> ba8f6f4ae254 ("iwlwifi: dbg: add dumping special device memory")
> reported at
>
> https://bugzilla.kernel.org/show_bug.cgi?id=210733
> https://bugzilla.suse.com/show_bug.cgi?id=1180344
>
> The problem seems to be an attempt to write terminating null character
> into a string which may be read only. There is also a proposed fix.
Can someone submit a proper patch, please? See instructions below how to
submit.
And please add Fixes tag to the commit log:
Fixes: ba8f6f4ae254 ("iwlwifi: dbg: add dumping special device memory")
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-01-12 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 11:58 regression in iwlwifi: page fault in iwl_dbg_tlv_alloc_region() (commit ba8f6f4ae254) Michal Kubecek
2021-01-12 11:33 ` Kalle Valo [this message]
2021-01-12 12:35 ` Takashi Iwai
2021-01-12 12:45 ` Kalle Valo
2021-01-12 12:58 ` Takashi Iwai
2021-01-12 15:46 ` Kalle Valo
2021-01-12 15:59 ` Takashi Iwai
2021-01-13 6:58 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9c2qtj9.fsf@tynnyri.adurom.net \
--to=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=mkubecek@suse.cz \
--cc=mordechay.goodstein@intel.com \
--cc=netdev@vger.kernel.org \
--cc=suse+build@de-korte.org \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).