netdev - Re: [PATCH] GRO: fix merging a paged skb after non-paged skbs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 8 Feb 2011 19:49:28 +1100
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Ben Hutchings <bhutchings@...arflare.com>
Cc:	Michal Schmidt <mschmidt@...hat.com>,
	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	linux-net-drivers@...arflare.com
Subject: Re: [PATCH] GRO: fix merging a paged skb after non-paged skbs

On Mon, Feb 07, 2011 at 08:39:20PM +0000, Ben Hutchings wrote:
> 
> That is indeed the case; commit da3bc07171dff957906cbe2ad5abb443eccf57c4
> made the following deletions:
> 
> -       /* Both our generic-LRO and SFC-SSR support skb and page based
> -        * allocation, but neither support switching from one to the
> -        * other on the fly. If we spot that the allocation mode has
> -        * changed, then flush the LRO state.
> -        */
> -       if (unlikely(channel->rx_alloc_pop_pages != (rx_buf->page != NULL))) {
> -               efx_flush_lro(channel);
> -               channel->rx_alloc_pop_pages = (rx_buf->page != NULL);
> -       }

Oops, sorry about that.

How about changing skb_gro_receive to detect such switches and
simply return an error, which should have the same effect as
flushing that flow?

Cheers,
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html