From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: open list <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>, Shuah Khan <shuah@kernel.org>,
patches@kernelci.org,
Ben Hutchings <ben.hutchings@codethink.co.uk>,
lkft-triage@lists.linaro.org,
linux- stable <stable@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>, Tejun Heo <tj@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
jouni.hogander@unikie.com,
"David S. Miller" <davem@davemloft.net>,
lukas.bulwahn@gmail.com
Subject: Re: [PATCH 4.14 000/211] 4.14.157-stable review
Date: Thu, 28 Nov 2019 11:51:37 +0530 [thread overview]
Message-ID: <CA+G9fYsuM-ALP_EtoFEzJiia26QnUvuKWsH0b-vi43Sp++es6A@mail.gmail.com> (raw)
In-Reply-To: <CA+G9fYtFNKTYiqm0Bvk_nqBTjsRMKTtNxr6PhE8YaDXFjqwhYQ@mail.gmail.com>
Hi Greg,
> Kernel BUG noticed on x86_64 device while booting 4.14.157-rc1 kernel.
The problematic patch is,
>> Jouni Hogander <jouni.hogander@unikie.com>
>> net-sysfs: Fix reference count leak in rx|netdev_queue_add_kobject
And this kernel panic is been fixed by below patch,
commit 48a322b6f9965b2f1e4ce81af972f0e287b07ed0
Author: Eric Dumazet <edumazet@google.com>
Date: Wed Nov 20 19:19:07 2019 -0800
net-sysfs: fix netdev_queue_add_kobject() breakage
kobject_put() should only be called in error path.
Fixes: b8eb718348b8 ("net-sysfs: Fix reference count leak in
rx|netdev_queue_add_kobject")
Signed-off-by: Eric Dumazet <edumazet@google.com>
Cc: Jouni Hogander <jouni.hogander@unikie.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
> Regressions (compared to build v4.14.156)
>
> [ 2.777657] BUG: unable to handle kernel NULL pointer dereference
> at 0000000000000090
> [ 2.785487] IP: kernfs_find_ns+0x18/0xf0
> [ 2.789408] PGD 0 P4D 0
> [ 2.791941] Oops: 0000 [#1] SMP PTI
> [ 2.795424] Modules linked in:
> [ 2.798474] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.14.157-rc1 #1
> [ 2.804906] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
> 2.2 05/23/2018
> [ 2.812288] task: ffff8e09ee250000 task.stack: ffffa0f900028000
> [ 2.818200] RIP: 0010:kernfs_find_ns+0x18/0xf0
<trim>
> [ 3.108995] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x00000009
> [ 3.108995]
> [ 3.118161] Kernel Offset: 0x1c400000 from 0xffffffff81000000
> (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
>
> Full test log,
> https://lkft.validation.linaro.org/scheduler/job/1026224#L793
>
--
Linaro LKFT
https://lkft.linaro.org
next prev parent reply other threads:[~2019-11-28 6:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191127203049.431810767@linuxfoundation.org>
2019-11-28 5:16 ` [PATCH 4.14 000/211] 4.14.157-stable review Naresh Kamboju
2019-11-28 6:21 ` Naresh Kamboju [this message]
2019-11-28 7:35 ` 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=CA+G9fYsuM-ALP_EtoFEzJiia26QnUvuKWsH0b-vi43Sp++es6A@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=ben.hutchings@codethink.co.uk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jouni.hogander@unikie.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=lukas.bulwahn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=patches@kernelci.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).