Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754349Ab2H0Uje (ORCPT ); Mon, 27 Aug 2012 16:39:34 -0400 Received: from mail-iy0-f174.google.com ([209.85.210.174]:53934 "EHLO mail-iy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754100Ab2H0Ujc (ORCPT ); Mon, 27 Aug 2012 16:39:32 -0400 Message-ID: <503BDAFF.9080904@lwfinger.net> Date: Mon, 27 Aug 2012 15:39:27 -0500 From: Larry Finger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Eric Dumazet CC: David Miller , 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" References: <50369925.3050705@lwfinger.net> <1345757200.5904.1890.camel@edumazet-glaptop> <50378B35.80307@lwfinger.net> <20120824.111948.680531915905273128.davem@davemloft.net> <5037A4B0.3080208@lwfinger.net> <1345825095.19483.19.camel@edumazet-glaptop> <1345825432.19483.20.camel@edumazet-glaptop> <5037B2AC.50704@lwfinger.net> <1345830424.19483.69.camel@edumazet-glaptop> <503BB49C.5010402@lwfinger.net> <1346091701.26634.6.camel@edumazet-glaptop> In-Reply-To: <1346091701.26634.6.camel@edumazet-glaptop> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1055 Lines: 26 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/