From: Yasushi SHOJI <yashi@atmark-techno.com>
To: sergei.shtylyov@cogentembedded.com
Cc: netdev@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH RFT v2] sh_eth: fix kernel oops in skb_put()
Date: Fri, 20 Nov 2015 20:18:58 +0900 [thread overview]
Message-ID: <878u5sdil9.wl@dns1.atmark-techno.com> (raw)
In-Reply-To: <564E0CA3.3020304@cogentembedded.com>
Hi Sergei,
On Fri, 20 Nov 2015 02:53:39 +0900,
Sergei Shtylyov wrote:
>
> Shoji-san, can I push this patch to net.git? I doubt that it has
> ill effects in itself -- the reason of the slowdown you're seeing
> should be somewhere else...
Sure. I've tested and the null access problem is gone for sure. I'm
pretty sure that the fix won't break anything.
It's going to take, however, some more time to pin down the slow down
problem. I'll report when I find the cause.
Thanks,
--
yashi
next prev parent reply other threads:[~2015-11-20 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 22:42 [PATCH RFT v2] sh_eth: fix kernel oops in skb_put() Sergei Shtylyov
2015-10-26 22:52 ` Yasushi SHOJI
2015-11-19 17:53 ` Sergei Shtylyov
2015-11-20 11:18 ` Yasushi SHOJI [this message]
2015-10-30 9:02 ` David Miller
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=878u5sdil9.wl@dns1.atmark-techno.com \
--to=yashi@atmark-techno.com \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.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).