[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230317063213.GC882@sol.localdomain>
Date: Thu, 16 Mar 2023 23:32:13 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: kernel test robot <yujie.liu@...el.com>
Cc: Kees Cook <keescook@...omium.org>, oe-lkp@...ts.linux.dev,
lkp@...el.com, Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Petr Mladek <pmladek@...e.com>,
Andrew Morton <akpm@...ux-foundation.org>,
tangmeng <tangmeng@...ontech.com>,
"Guilherme G. Piccoli" <gpiccoli@...lia.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Tiezhu Yang <yangtiezhu@...ngson.cn>,
Luis Chamberlain <mcgrof@...nel.org>,
linux-hardening@...r.kernel.org, linux-kernel@...r.kernel.org,
aliyunlinux2-dev@...ux.alibaba.com, jane.lv@...el.com
Subject: Re: [linux-stable-rc:linux-4.19.y] [panic] 4d00e68cfc:
WARNING:at_fs/sysfs/file.c:#sysfs_emit_at
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
Powered by blists - more mailing lists