From: Simon Horman <simon.horman@corigine.com>
To: void0red <void0red@gmail.com>
Cc: lorenzo.bianconi@redhat.com,
angelogioacchino.delregno@collabora.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, kvalo@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-wireless@vger.kernel.org, lorenzo@kernel.org,
matthias.bgg@gmail.com, nbd@nbd.name, netdev@vger.kernel.org,
pabeni@redhat.com, ryder.lee@mediatek.com,
sean.wang@mediatek.com, shayne.chen@mediatek.com
Subject: Re: [PATCH v3] wifi: mt76: handle failure of vzalloc in mt7615_coredump_work
Date: Mon, 6 Mar 2023 12:00:02 +0100 [thread overview]
Message-ID: <ZAXHsidkn1g7YMeo@corigine.com> (raw)
In-Reply-To: <20230227144823.947648-1-void0red@gmail.com>
On Mon, Feb 27, 2023 at 10:48:23PM +0800, void0red wrote:
> From: Kang Chen <void0red@gmail.com>
>
> vzalloc may fails, dump might be null and will cause
> illegal address access later.
>
> Link: https://lore.kernel.org/all/Y%2Fy5Asxw3T3m4jCw@lore-desk
> Fixes: d2bf7959d9c0 ("mt76: mt7663: introduce coredump support")
> Signed-off-by: Kang Chen <void0red@gmail.com>
Reviewed-by: Simon Horman <simon.horman@corigine.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-03-06 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 11:57 [PATCH] wifi: mt76: add a check of vzalloc in mt7615_coredump_work Kang Chen
2023-02-27 13:33 ` Lorenzo Bianconi
2023-02-27 13:52 ` [PATCH v2] " void0red
2023-02-27 14:06 ` Lorenzo Bianconi
2023-02-27 14:28 ` Kang Chen
2023-02-27 14:48 ` [PATCH v3] wifi: mt76: handle failure " void0red
2023-03-06 11:00 ` Simon Horman [this message]
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=ZAXHsidkn1g7YMeo@corigine.com \
--to=simon.horman@corigine.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=void0red@gmail.com \
/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).