mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rudraksha Gupta <guptarud@gmail.com>
To: Stephan Gerhold <stephan.gerhold@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Andrew Halaney <ahalaney@redhat.com>,
	Elliot Berman <quic_eberman@quicinc.com>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	"Linux regression tracking (Thorsten Leemhuis)"
	<regressions@leemhuis.info>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v2 2/2] firmware: qcom: scm: fall back to kcalloc() for no SCM device bound
Date: Mon, 16 Sep 2024 23:28:25 -0700	[thread overview]
Message-ID: <994f9631-f836-47de-a275-5c20183b84e5@gmail.com> (raw)
In-Reply-To: <ZuhgV1vicIFzPGI-@linaro.org>

> Actually, taking only the first patch in this series should be enough to
> fix the crash Rudraksha reported. None of the older platforms should
> ever reach into this if statement. I think the rough story is:

Yep, just tested this right now, and the first patch alone seems to do 
the trick!



  reply	other threads:[~2024-09-17  6:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11  9:07 [PATCH v2 0/2] firmware: qcom: scm: fix SMC calls on ARM32 Bartosz Golaszewski
2024-09-11  9:07 ` [PATCH v2 1/2] firmware: qcom: scm: fix a NULL-pointer dereference Bartosz Golaszewski
2024-09-11 10:49   ` Dmitry Baryshkov
2024-09-16 16:30   ` Stephan Gerhold
2024-09-11  9:07 ` [PATCH v2 2/2] firmware: qcom: scm: fall back to kcalloc() for no SCM device bound Bartosz Golaszewski
2024-09-16 16:44   ` Stephan Gerhold
2024-09-17  6:28     ` Rudraksha Gupta [this message]
2024-09-17 10:17     ` Bartosz Golaszewski
2024-09-18  8:18       ` Stephan Gerhold
2024-09-25  9:35 ` [PATCH v2 0/2] firmware: qcom: scm: fix SMC calls on ARM32 Linux regression tracking (Thorsten Leemhuis)
2024-09-25  9:45   ` Bartosz Golaszewski

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=994f9631-f836-47de-a275-5c20183b84e5@gmail.com \
    --to=guptarud@gmail.com \
    --cc=ahalaney@redhat.com \
    --cc=andersson@kernel.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_eberman@quicinc.com \
    --cc=regressions@leemhuis.info \
    --cc=stephan.gerhold@linaro.org \
    /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

all inboxes | Powered by JetHome®