linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eran Liberty <liberty@extricom.com>
To: emin ak <eminak71@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	galak@kernel.crashing.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gainfar.c : skb_over_panic (kernel-2.6.32.15)
Date: Sun, 03 Oct 2010 11:32:17 +0200	[thread overview]
Message-ID: <4CA84DA1.1070206@extricom.com> (raw)
In-Reply-To: <AANLkTikXj3cAkrMMUP2_TGSFYQY9=oPg8QxOU-jYUjnR@mail.gmail.com>

Dear Amin Ak,

A patch has been posted both to the most recent kernel tree at the time 
and to the long term 2.6.32.X branch. At which point it is out of mine 
and in the capable hands of the maintainers.

If needs be, I am willing to repost the patches even though they are 
still out there and probably still fresh enough.

If you apply them and solve your own private overpanic maybe "ack"ing 
the patch will expedite its trip into the kernel kingdom.

-- Liberty

emin ak wrote:
> Hi Eran, David
> This bug still exits on current both stable and rc kernel releases
> reported on the mail list.
> http://lkml.org/lkml/2010/9/28/178
> Is there any merge plan this patch to current kernel.
> Regards
>
>
> 2010/6/29 Eran Liberty <liberty@extricom.com>:
>   
>> David Miller wrote:
>>     
>>> From: Eran Liberty <liberty@extricom.com>
>>> Date: Mon, 28 Jun 2010 10:57:08 +0300
>>>
>>>       
>>>> This code has proved to be insufficient and produce
>>>> skb_over_panic. The proposed patch fix this.
>>>>         
>>> Then you have to post a patch relative to the current code, rather than
>>> against the code as it was several releases ago.
>>>
>>> Your patch didn't apply, so I can't use it.
>>>
>>>       
>> Upon cleaning up my patch for the latest kernel I realized I do not
>> like: the previous partial fix, the fix in ucc_geth.c, the fix in the
>> current latest kernel, and my own previously proposed patch. They all
>> tried to undo the alignment skb_reserve done in gfar_new_skb() before
>> queuing the skb into the rw_recycle, because upon getting a new one in
>> gfar_new_skb() if the skb is from the rx_recycle pool rather then newly
>> allocated it is reserved twice.
>>
>> Instead of trying to undo the skb_reserve this proposed patch will make
>> sure the alignment skb_reserve is done once, upon allocating the skb and
>> not when taken out of the rx_recycle pool. Eliminating the need to undo
>> anything before queue skb back to the pool.
>>
>> This patch will apply cleanly against the 2.6.32.15. Another patch will
>> be submitted separately for the current Linus tree.
>>
>> -- Liberty
>>
>> Signed-off-by: Eran Liberty <liberty@extricom.com>
>>     


  reply	other threads:[~2010-10-03 10:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-24  9:53 [PATCH] gainfar.c : skb_over_panic (kernel-2.6.32.15) Eran Liberty
2010-06-24 21:52 ` David Miller
2010-06-28  7:57   ` Eran Liberty
2010-06-28 18:33     ` David Miller
2010-06-29 15:42       ` Eran Liberty
2010-06-29 16:20         ` [PATCH] gainfar.c : code cleanup Eran Liberty
2010-09-29  0:35         ` [PATCH] gainfar.c : skb_over_panic (kernel-2.6.32.15) emin ak
2010-10-03  9:32           ` Eran Liberty [this message]
2010-10-03 10:54             ` emin ak
2010-10-03 14:48               ` Eran Liberty

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=4CA84DA1.1070206@extricom.com \
    --to=liberty@extricom.com \
    --cc=davem@davemloft.net \
    --cc=eminak71@gmail.com \
    --cc=galak@kernel.crashing.org \
    --cc=linux-kernel@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).