All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jiri Olsa <jolsa@redhat.com>
Cc: eric.dumazet@gmail.com, jengelh@medozas.de, davem@redhat.com,
	netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
	linux-man@vger.kernel.org
Subject: Re: [PATCH] net: ipv4,nodefrag: check socket type before touching nodefrag flag
Date: Wed, 22 Sep 2010 08:59:55 +0200	[thread overview]
Message-ID: <4C99A96B.4020604@trash.net> (raw)
In-Reply-To: <1284974876-4596-1-git-send-email-jolsa@redhat.com>

Am 20.09.2010 11:27, schrieb Jiri Olsa:
> we need to check proper socket type within ipv4_conntrack_defrag
> function before referencing the nodefrag flag.
> 
> For example the tun driver receive path produces skbs with
> AF_UNSPEC socket type, and so current code is causing unwanted
> fragmented packets going out.

Looks good. Applied, thanks.


      reply	other threads:[~2010-09-22  6:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20  9:27 [PATCH] net: ipv4,nodefrag: check socket type before touching nodefrag flag Jiri Olsa
2010-09-22  6:59 ` Patrick McHardy [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=4C99A96B.4020604@trash.net \
    --to=kaber@trash.net \
    --cc=davem@redhat.com \
    --cc=eric.dumazet@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=jolsa@redhat.com \
    --cc=linux-man@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.