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, stephen@networkplumber.org
Subject: Re: [BUG]: Kernel 4.9: Kernel crash at fs/sysfs/file.c : sysfs_kf_seq_show
Date: Wed, 13 Jan 2021 13:28:22 +0100 [thread overview]
Message-ID: <X/7nZjjJ3doGT3XO@kroah.com> (raw)
In-Reply-To: <X/7m4787HEIcxZzm@kroah.com>
On Wed, Jan 13, 2021 at 01:26:11PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Jan 13, 2021 at 05:35:18PM +0530, Pintu Agarwal wrote:
> > On Tue, 12 Jan 2021 at 17:39, Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > >
> > > 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.
> > > >
> >
> > I see that this issue was reported earlier as well by others.
> > https://syzkaller.appspot.com/bug?id=2ec2a9da5c711df3d3d12071bac487b96e75e103
> > https://gitlab.freedesktop.org/drm/amd/-/issues/413
> > https://bugzilla.redhat.com/show_bug.cgi?id=1615070
> >
> > So it seems to be common issue and thus I wanted to check here if its similar.
>
> It's "common" in that this is core kernel code that any number of
> drivers could be causing to work incorrectly. Try fixing up the driver
> code, and odds are, that will fix this issue.
>
> good luck, and again, go ask for support from your vendor, you are
> paying for that!
And, if you look close at the above links, you will see where the error
is, and what the out-of-tree code needs to to do be fixed up properly.
An exercise for that is left for the vendor :)
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: indranilghsh428@gmail.com, linux-arm-msm@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
landy.gross@linaro.org, stephen@networkplumber.org,
David Brown <david.brown@linaro.org>,
linux-soc@vger.kernel.org,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [BUG]: Kernel 4.9: Kernel crash at fs/sysfs/file.c : sysfs_kf_seq_show
Date: Wed, 13 Jan 2021 13:28:22 +0100 [thread overview]
Message-ID: <X/7nZjjJ3doGT3XO@kroah.com> (raw)
In-Reply-To: <X/7m4787HEIcxZzm@kroah.com>
On Wed, Jan 13, 2021 at 01:26:11PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Jan 13, 2021 at 05:35:18PM +0530, Pintu Agarwal wrote:
> > On Tue, 12 Jan 2021 at 17:39, Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > >
> > > 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.
> > > >
> >
> > I see that this issue was reported earlier as well by others.
> > https://syzkaller.appspot.com/bug?id=2ec2a9da5c711df3d3d12071bac487b96e75e103
> > https://gitlab.freedesktop.org/drm/amd/-/issues/413
> > https://bugzilla.redhat.com/show_bug.cgi?id=1615070
> >
> > So it seems to be common issue and thus I wanted to check here if its similar.
>
> It's "common" in that this is core kernel code that any number of
> drivers could be causing to work incorrectly. Try fixing up the driver
> code, and odds are, that will fix this issue.
>
> good luck, and again, go ask for support from your vendor, you are
> paying for that!
And, if you look close at the above links, you will see where the error
is, and what the out-of-tree code needs to to do be fixed up properly.
An exercise for that is left for the vendor :)
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-01-13 12:27 UTC|newest]
Thread overview: 14+ 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:01 ` Pintu Agarwal
2021-01-12 12:08 ` Greg Kroah-Hartman
2021-01-12 12:08 ` Greg Kroah-Hartman
2021-01-12 12:10 ` Greg Kroah-Hartman
2021-01-12 12:10 ` Greg Kroah-Hartman
2021-01-13 12:05 ` Pintu Agarwal
2021-01-13 12:05 ` Pintu Agarwal
2021-01-13 12:26 ` Greg Kroah-Hartman
2021-01-13 12:26 ` Greg Kroah-Hartman
2021-01-13 12:28 ` Greg Kroah-Hartman [this message]
2021-01-13 12:28 ` Greg Kroah-Hartman
2021-01-13 17:44 ` Pintu Agarwal
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/7nZjjJ3doGT3XO@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 \
--cc=stephen@networkplumber.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.