linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	ncardwell@google.com, linville@tuxdriver.com,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Regression associated with commit c8628155ece3 - "tcp: reduce out_of_order memory use"
Date: Mon, 27 Aug 2012 15:39:27 -0500	[thread overview]
Message-ID: <503BDAFF.9080904@lwfinger.net> (raw)
In-Reply-To: <1346091701.26634.6.camel@edumazet-glaptop>

On 08/27/2012 01:21 PM, Eric Dumazet wrote:
> On Mon, 2012-08-27 at 12:55 -0500, Larry Finger wrote:
>
>> I have prepared a patch to fix all the unchecked allocations.
>>
>> Over the weekend I made some progress. To test the latest vendor driver, I
>> installed a 32-bit system. Their driver is not compatible with a 64-bit system.
>> I found that not only did the vendor driver work with secure sites, but so did
>> the in-kernel version. I now have tcpdump output for the 32-bit case that works,
>> and the 64-bit case that fails. It seems likely that I missed some 32/64 bit
>> incompatibility when I did the conversion.
>>
>> Thanks for all your help in trying to resolve this issue.
>
> Interesting, so these 32/64 bits problems did not happen in prior
> kernels ? (< 3.4 )

Prior kernels are OK.

Larry


  reply	other threads:[~2012-08-27 20:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22  4:07 Regression associated with commit c8628155ece3 - "tcp: reduce out_of_order memory use" Larry Finger
2012-08-22  4:26 ` David Miller
2012-08-22  5:15 ` Eric Dumazet
2012-08-22 16:00   ` Larry Finger
2012-08-22 21:33   ` Larry Finger
2012-08-23  4:03     ` Eric Dumazet
2012-08-23 20:57       ` Larry Finger
2012-08-23 21:26         ` Eric Dumazet
2012-08-24 14:09           ` Larry Finger
2012-08-24 14:55             ` Eric Dumazet
2012-08-24 15:49               ` Larry Finger
2012-08-24 16:01                 ` Eric Dumazet
2012-08-24 16:29                   ` Larry Finger
2012-08-24 15:19             ` David Miller
2012-08-24 15:58               ` Larry Finger
2012-08-24 16:18                 ` Eric Dumazet
2012-08-24 16:23                   ` Eric Dumazet
2012-08-24 16:58                     ` Larry Finger
2012-08-24 17:47                       ` Eric Dumazet
2012-08-27 17:55                         ` Larry Finger
2012-08-27 18:21                           ` Eric Dumazet
2012-08-27 20:39                             ` Larry Finger [this message]
2012-09-10  8:39                           ` Eric Dumazet
2012-09-10 14:53                             ` Larry Finger
2012-09-10 15:04                               ` Eric Dumazet
2012-09-10 17:55                                 ` [PATCH] staging: r8712u: fix bug in r8712_recv_indicatepkt() Eric Dumazet
2012-09-10 18:34                                   ` Larry Finger

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=503BDAFF.9080904@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=ncardwell@google.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).