From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: "Koehrer Mathias (ETAS/ESW5)" <mathias.koehrer@etas.com>,
Nick Krause <xerofoify@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] Fix e1000e with Intel 82572EI that has no hardware timestamp support
Date: Wed, 06 Aug 2014 18:05:50 +0400 [thread overview]
Message-ID: <53E2363E.9040208@cogentembedded.com> (raw)
In-Reply-To: <ef09199e48ab4d4a80c4ba554c9e3853@FE-MBX1012.de.bosch.com>
Hello.
On 8/6/2014 5:56 PM, Koehrer Mathias (ETAS/ESW5) wrote:
> With the Intel 82527EI (driver: e1000e) there is an issue when running the ptpd2 program, that leads to a kernel oops.
> The reason is here that in e1000_xmit_frame() a work queue will be scheduled that has not been initialized in this case.
> The work queue "tx_hwstamp_work" will only be initialized if adapter->flags & FLAG_HAS_HW_TIMESTAMP set.
> This check is missing in e1000_xmit_frame().
Please wrap your changelog at 80 columns or less.
> The following patch adds the missing check.
> Signed-off-by: Mathias Koehrer <mathias.koehrer@etas.com>
> ---
> drivers/net/ethernet/intel/e1000e/netdev.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
> Index: linux-3.12.26/drivers/net/ethernet/intel/e1000e/netdev.c
> ===================================================================
> --- linux-3.12.26.orig/drivers/net/ethernet/intel/e1000e/netdev.c 2014-08-04 10:56:56.000000000 +0200
> +++ linux-3.12.26/drivers/net/ethernet/intel/e1000e/netdev.c 2014-08-06 15:15:42.000000000 +0200
> @@ -5549,7 +5549,8 @@
> count = e1000_tx_map(tx_ring, skb, first, adapter->tx_fifo_limit,
> nr_frags);
> if (count) {
> - if (unlikely((skb_shinfo(skb)->tx_flags & SKBTX_HW_TSTAMP) &&
Your mailer has corrupted the patch -- all tabs were converted to spaces.
> + if ((adapter->flags & FLAG_HAS_HW_TIMESTAMP) &&
> + unlikely((skb_shinfo(skb)->tx_flags & SKBTX_HW_TSTAMP) &&
When you break the line with the *if* statement, continuation lines should
start on a column right after ( above, according to the networking coding style.
WBR, Sergei
next prev parent reply other threads:[~2014-08-06 14:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 13:56 [PATCH] Fix e1000e with Intel 82572EI that has no hardware timestamp support Koehrer Mathias (ETAS/ESW5)
2014-08-06 13:56 ` Koehrer Mathias (ETAS/ESW5)
2014-08-06 14:05 ` Sergei Shtylyov [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-06 14:27 Koehrer Mathias (ETAS/ESW5)
2014-08-06 14:30 ` Sergei Shtylyov
2014-08-06 15:09 ` Henrique de Moraes Holschuh
2014-08-06 15:21 ` Alexander Duyck
2014-08-06 15:26 ` Alexander Duyck
[not found] ` <CAPDOMVgHmQeqOGj1MegRa=gusGXMn5t7cwCNnutpc1_q_fzyYg@mail.gmail.com>
2014-08-06 20:19 ` Alexander Duyck
2014-08-06 14:32 Koehrer Mathias (ETAS/ESW5)
2014-08-06 19:17 ` Richard Cochran
[not found] ` <CAPDOMVjYkfM49E9DM0=SDDRncLQbXxR8NQE9SrsW++YycMGU5w@mail.gmail.com>
2014-08-06 19:32 ` Richard Cochran
[not found] ` <CAPDOMViFCifeUoOgExuG7Q6_ObGj20g59siyMxWeKN=Zr2Kbdg@mail.gmail.com>
2014-08-06 19:54 ` Richard Cochran
2014-08-07 6:10 ` Koehrer Mathias (ETAS/ESW5)
2014-08-07 6:20 ` Jeff Kirsher
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=53E2363E.9040208@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.koehrer@etas.com \
--cc=netdev@vger.kernel.org \
--cc=xerofoify@gmail.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 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.