linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Raphael G <raphael.glon@corp.ovh.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
	"marcin wojtas" <mw@semihalf.com>,
	davem@davemloft.net,
	"Grégory Clement" <gregory.clement@free-electrons.com>
Subject: Re: double free issue, mvpp2 driver, armada375 modules
Date: Tue, 13 Dec 2016 17:55:18 +0100	[thread overview]
Message-ID: <20161213175518.3b3b1ff8@free-electrons.com> (raw)
In-Reply-To: <57272206.6070703@corp.ovh.com>

Hello,

On Mon, 2 May 2016 11:46:46 +0200, Raphael G wrote:

> enclosed the kernel panic we obtain after boot with a slightly patched 
> upstream kernel (4.5.2).
> 
> (as well as the patchset applied to the upstream kernel, so that you can 
> know which code we are talking about. Too bad we cannot use the upstream 
> kernel but we had no choice about this + we're no experts so we rely on 
> provided patches, adapted to our bootloader and hardware for this)
> 
> Reproduce:
> boot on kernel on an armada375 module, connect to it, launch a top in 
> commandline
> 
> As seen with Marcin Wojtas, reverting commit 
> e864b4c7b184bde36fa6a02bb3190983d2f796f9 fixes this issue.
> 
> Reporting upstream so that you can decide what should be done next

Thanks for your report. I have finally submitted a fix for this issue.
You can find it at:

  http://lists.infradead.org/pipermail/linux-arm-kernel/2016-December/473989.html

If you have the time to test it and report back, it would be very
useful.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2016-12-13 16:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02  9:46 double free issue, mvpp2 driver, armada375 modules Raphael G
2016-12-13 16:55 ` Thomas Petazzoni [this message]

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=20161213175518.3b3b1ff8@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=davem@davemloft.net \
    --cc=gregory.clement@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mw@semihalf.com \
    --cc=netdev@vger.kernel.org \
    --cc=raphael.glon@corp.ovh.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).