From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Oleksij Rempel <o.rempel@pengutronix.de>
Cc: dev.kurt@vandijck-laurijssen.be, Netdev <netdev@vger.kernel.org>,
lkft-triage@lists.linaro.org, linux-can@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>,
wg@grandegger.com
Subject: Re: [RFC] can: can_create_echo_skb(): fix echo skb generation: always use skb_clone()
Date: Mon, 3 Feb 2020 14:52:54 +0100 [thread overview]
Message-ID: <b0aa1582-98d0-6929-da8d-879151c49654@pengutronix.de> (raw)
In-Reply-To: <7ee9df43-2efb-ba57-c8a9-301bae12c0d7@pengutronix.de>
On 2/3/20 2:48 PM, Marc Kleine-Budde wrote:
>>> WARNING: CPU: 0 PID: 293 at lib/refcount.c:25 refcount_warn_saturate+0x108/0x174
>>> refcount_t: addition on 0; use-after-free.
>>
>> FYI,
>> This issue noticed in our Linaro test farm
>> On linux next version 5.5.0-next-20200203 running on beagleboard x15 arm device.
>>
>> Thanks for providing fix for this case.
Please look closely at your backtraces, they are totally unrelated. It
seems the whole culprit in your testcase fails with:
> [ 0.000000] OF: ERROR: Bad of_node_put() on /ocp/interconnect@4a000000/segment@0/target-module@8000/cm_core@0/l4per-cm@1700/l4per-clkctrl@28
...the rest are subsequent faults.
> Can we add your Tested-by to the patch?
Answering myself: NO!
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2020-02-03 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 13:26 [RFC] can: can_create_echo_skb(): fix echo skb generation: always use skb_clone() Oleksij Rempel
2020-02-03 13:43 ` Naresh Kamboju
2020-02-03 13:48 ` Marc Kleine-Budde
2020-02-03 13:52 ` Marc Kleine-Budde [this message]
2020-02-03 14:36 ` Naresh Kamboju
2020-02-14 12:09 ` Oleksij Rempel
2020-10-16 19:36 ` Marc Kleine-Budde
2020-10-17 19:13 ` Oliver Hartkopp
2020-10-18 8:46 ` Oliver Hartkopp
2020-10-19 6:28 ` Marc Kleine-Budde
2020-10-19 6:53 ` Oliver Hartkopp
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=b0aa1582-98d0-6929-da8d-879151c49654@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=dev.kurt@vandijck-laurijssen.be \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=wg@grandegger.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;
as well as URLs for NNTP newsgroup(s).