From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
landy.gross@linaro.org, David Brown <david.brown@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
indranilghsh428@gmail.com
Subject: Re: [BUG]: Kernel 4.9: Kernel crash at fs/sysfs/file.c : sysfs_kf_seq_show
Date: Tue, 12 Jan 2021 13:10:23 +0100 [thread overview]
Message-ID: <X/2Rr5LDNbxGz456@kroah.com> (raw)
In-Reply-To: <CAOuPNLiUBhJdsgw9bjQxxhkeBHQFoE_vN_Na6kw3ksr89r+HOg@mail.gmail.com>
On Tue, Jan 12, 2021 at 05:31:54PM +0530, Pintu Agarwal wrote:
> Hi,
>
> I am using Kernel: 4.9.217 for one of the ARM32 boards for Qualcomm SOC.
> https://github.com/android-linux-stable/msm-4.9
>
> But I think this is a general bug applicable to :Kernel 4.9 under
> fs/sysfs/file.c
> So, I wanted to quickly check here if others are familiar with this
> issue and if it is fixed already.
> Note, this issue does not occur in 4.14 Kernel.
>
> When I execute below command, the Kernel is crashing.
> I tried to add few debug prints to find more details. I see that the
> ops->show pointer is not valid (seems corrupted).
> So I wanted to understand how this can happen only for this particular node.
> Other sysfs entries are working fine.
>
> # cat /sys/power/rpmh_stats/master_stats
Also note that this file is not in the upstream kernel tree, so there's
not much we can do about this either...
good luck!
greg k-h
next prev parent reply other threads:[~2021-01-12 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 12:01 [BUG]: Kernel 4.9: Kernel crash at fs/sysfs/file.c : sysfs_kf_seq_show Pintu Agarwal
2021-01-12 12:08 ` Greg Kroah-Hartman
2021-01-12 12:10 ` Greg Kroah-Hartman [this message]
2021-01-13 12:05 ` Pintu Agarwal
2021-01-13 12:26 ` Greg Kroah-Hartman
2021-01-13 12:28 ` Greg Kroah-Hartman
2021-01-13 17:44 ` Pintu Agarwal
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=X/2Rr5LDNbxGz456@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=david.brown@linaro.org \
--cc=indranilghsh428@gmail.com \
--cc=landy.gross@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=pintu.ping@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