From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG arm-soc] mvneta: tx queue done sometimes causes kernel panic
Date: Sat, 16 Feb 2013 02:20:43 +0100 [thread overview]
Message-ID: <20130216022043.65d5c940@skate> (raw)
In-Reply-To: <1360947132.19353.15.camel@edumazet-glaptop>
Hello,
On Fri, 15 Feb 2013 08:52:12 -0800, Eric Dumazet wrote:
> Driver is buggy, as TX completion can happen both from ndo_start_xmit()
> and a timer, and there is no spinlock or appropriate synchro.
Yes, it is a known issue. I did post a patch fixing the problem on
netdev@ a while ago [1], but while it was fixing the problem, it wasn't
considered the right approach. Being busy with other Marvell Armada
370/XP developments, I haven't yet had the time to investigate the
issue again.
[1] https://patchwork.kernel.org/patch/1941601/
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
linux-arm-kernel@lists.infradead.org,
"yrl.pp-manager.tt@hitachi.com" <yrl.pp-manager.tt@hitachi.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>
Subject: Re: [BUG arm-soc] mvneta: tx queue done sometimes causes kernel panic
Date: Sat, 16 Feb 2013 02:20:43 +0100 [thread overview]
Message-ID: <20130216022043.65d5c940@skate> (raw)
In-Reply-To: <1360947132.19353.15.camel@edumazet-glaptop>
Hello,
On Fri, 15 Feb 2013 08:52:12 -0800, Eric Dumazet wrote:
> Driver is buggy, as TX completion can happen both from ndo_start_xmit()
> and a timer, and there is no spinlock or appropriate synchro.
Yes, it is a known issue. I did post a patch fixing the problem on
netdev@ a while ago [1], but while it was fixing the problem, it wasn't
considered the right approach. Being busy with other Marvell Armada
370/XP developments, I haven't yet had the time to investigate the
issue again.
[1] https://patchwork.kernel.org/patch/1941601/
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-02-16 1:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 7:40 [BUG arm-soc] mvneta: tx queue done sometimes causes kernel panic Masami Hiramatsu
2013-02-15 16:52 ` Eric Dumazet
2013-02-15 16:52 ` Eric Dumazet
2013-02-16 1:20 ` Thomas Petazzoni [this message]
2013-02-16 1:20 ` Thomas Petazzoni
2013-02-18 14:34 ` Masami Hiramatsu
2013-02-18 14:34 ` Masami Hiramatsu
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=20130216022043.65d5c940@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.