From: Joyce Yu <Joyce.Yu@Sun.COM>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [Fwd: [PATCH] [NIU] VLAN does not work with niu driver]
Date: Mon, 19 Oct 2009 15:12:49 -0700 [thread overview]
Message-ID: <4ADCE461.9080809@Sun.COM> (raw)
In-Reply-To: <20091016.174008.193713863.davem@davemloft.net>
Here was what happened to this patch:
I got system hard hung a couple of times when testing the niu driver
with "__pskb_pull_tail(skb, min(len, VLAN_ETH_HLEN))" fix. I thought
that the fix was not working at the time, so I came up with the fixes
moving around the pointers. I didn't see the hard hung with that code.
When you asked me to explain the fix, I had the second thought to
re-test the "__pskb_pull_tail(skb, min(len, VLAN_ETH_HLEN))" fix. I
didn't experience any hard hung any more. I also asked our QA to test it
and didn't find any problem. I guess the hard hung may due to
rmmod/insmod, ifconfig up/down using different fixes so many times and
that may cause memory corruptions.
Regards,
Joyce
On 10/16/09 05:40 PM, David Miller wrote:
> From: Joyce Yu <Joyce.Yu@Sun.COM>
> Date: Fri, 16 Oct 2009 09:21:46 -0700
>
>> Can this patch be accepted and integrated to the main tree?
>
> Well, what happened to all of those page fragment modifications?
>
> They all of a sudden are no longer necessary? Why?
>
> I'm not going to apply this patch until you start explaining
> why these things are being done, or not done. And you must
> add some more text to your commit messages so that you explain
> your change sufficiently.
>
> Thank you.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
prev parent reply other threads:[~2009-10-19 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 16:21 [Fwd: [PATCH] [NIU] VLAN does not work with niu driver] Joyce Yu
2009-10-17 0:40 ` David Miller
2009-10-19 22:12 ` Joyce Yu [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=4ADCE461.9080809@Sun.COM \
--to=joyce.yu@sun.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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 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).