From: Eric Biggers <ebiggers@kernel.org>
To: kernel test robot <yujie.liu@intel.com>
Cc: Kees Cook <keescook@chromium.org>,
oe-lkp@lists.linux.dev, lkp@intel.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Petr Mladek <pmladek@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
tangmeng <tangmeng@uniontech.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Tiezhu Yang <yangtiezhu@loongson.cn>,
Luis Chamberlain <mcgrof@kernel.org>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org,
aliyunlinux2-dev@linux.alibaba.com, jane.lv@intel.com
Subject: Re: [linux-stable-rc:linux-4.19.y] [panic] 4d00e68cfc: WARNING:at_fs/sysfs/file.c:#sysfs_emit_at
Date: Thu, 16 Mar 2023 23:32:13 -0700 [thread overview]
Message-ID: <20230317063213.GC882@sol.localdomain> (raw)
In-Reply-To: <202303141634.1e64fd76-yujie.liu@intel.com>
On Tue, Mar 14, 2023 at 04:34:22PM +0800, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed WARNING:at_fs/sysfs/file.c:#sysfs_emit_at due to commit (built with gcc-11):
>
> commit: 4d00e68cfcfd91d3a8c794d47617429a96d623ed ("panic: Expose "warn_count" to sysfs")
> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
It turns out this is a longstanding bug in 4.19.y and 4.14.y caused by a bad
backport, which is not actually related to the above commit (or the patch series
that contained it) at all. I've sent out fixes:
4.19: https://lore.kernel.org/r/20230317062743.313169-1-ebiggers@kernel.org
4.14: https://lore.kernel.org/r/20230317062801.313217-1-ebiggers@kernel.org
- Eric
next prev parent reply other threads:[~2023-03-17 6:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 8:34 [linux-stable-rc:linux-4.19.y] [panic] 4d00e68cfc: WARNING:at_fs/sysfs/file.c:#sysfs_emit_at kernel test robot
2023-03-17 6:32 ` Eric Biggers [this message]
2023-03-17 6:50 ` Greg Kroah-Hartman
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=20230317063213.GC882@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aliyunlinux2-dev@linux.alibaba.com \
--cc=bigeasy@linutronix.de \
--cc=gpiccoli@igalia.com \
--cc=gregkh@linuxfoundation.org \
--cc=jane.lv@intel.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mcgrof@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=pmladek@suse.com \
--cc=tangmeng@uniontech.com \
--cc=yangtiezhu@loongson.cn \
--cc=yujie.liu@intel.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