From: Sudeep Holla <sudeep.holla@arm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: NULL pointer dereference in cpufreq_set_policy
Date: Tue, 15 Oct 2019 17:17:59 +0100 [thread overview]
Message-ID: <20191015161759.GA16693@bogus> (raw)
In-Reply-To: <CAJZ5v0g04KoF3pQk4=3cTyyPsKdgLV+ZrO63k44HvySss1xJ=g@mail.gmail.com>
On Tue, Oct 15, 2019 at 06:08:14PM +0200, Rafael J. Wysocki wrote:
> On Tue, Oct 15, 2019 at 5:57 PM Sudeep Holla <sudeep.holla@arm.com> wrote:
> >
> > Hi Viresh,
> >
> > I was trying to unify Vexpress SPC driver and arm_big_little generic
> > driver as it's the only user of bL driver and switcher in the mainline.
> > I did this a while ago(v5.3) and encountered the kernel crash with NULL
> > pointer reference(crash log with some debug enabled below).
> >
> > Since dev_pm_qos_* was added in v5.3 with the Commit 18c49926c4bf
> > ("cpufreq: Add QoS requests for userspace constraints"), I just tried
> > reverting that and it fixed the crash. I haven't spent much time
> > debugging, since it has been for a while I wanted to report it.
>
> This looks like another manifestation of the bug discussed here:
> https://lore.kernel.org/linux-pm/5ad2624194baa2f53acc1f1e627eb7684c577a19.1562210705.git.viresh.kumar@linaro.org/T/#md2d89e95906b8c91c15f582146173dce2e86e99f
Indeed, it reminded me to dig up the setup, try again and report this
bug before I forget again about the issue as this platform is in back
burner and not priority :)
--
Regards,
Sudeep
prev parent reply other threads:[~2019-10-15 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 15:57 NULL pointer dereference in cpufreq_set_policy Sudeep Holla
2019-10-15 16:08 ` Rafael J. Wysocki
2019-10-15 16:17 ` Sudeep Holla [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=20191015161759.GA16693@bogus \
--to=sudeep.holla@arm.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=viresh.kumar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.