netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Bizon <mbizon@freebox.fr>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "Patrick McHardy" <kaber@trash.net>,
	"Eric Dumazet" <edumazet@google.com>,
	davem@davemloft.net, netdev <netdev@vger.kernel.org>,
	"Maciej Żenczykowski" <maze@google.com>
Subject: Re: problem forwarding IP fragments with DF bit set (caused by ipv4: fix path MTU discovery with connection tracking)
Date: Wed, 30 Apr 2014 16:34:51 +0200	[thread overview]
Message-ID: <1398868491.5474.10.camel@sakura.staff.proxad.net> (raw)
In-Reply-To: <1398785841.29914.146.camel@edumazet-glaptop2.roam.corp.google.com>


On Tue, 2014-04-29 at 08:37 -0700, Eric Dumazet wrote:

> Hmm... maybe its finally time to rename local_df to ignore_df, as
> Maze suggested some time ago ...

It would have indeed helped me to understand the purpose of this flag at
first glance.

About the patch I sent, I'm not well equipped to test mainline kernels
wrt the bug I reported (it does not boot on my embedded device), so I'd
prefer someone else to cook the patch and actually test it.

Thanks,

-- 
Maxime

      parent reply	other threads:[~2014-04-30 14:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 16:37 problem forwarding IP fragments with DF bit set (caused by ipv4: fix path MTU discovery with connection tracking) Maxime Bizon
2014-04-28 17:59 ` Maxime Bizon
2014-04-29 14:35   ` Patrick McHardy
2014-04-29 14:33 ` Patrick McHardy
2014-04-29 14:42   ` Maxime Bizon
2014-04-29 14:45     ` Patrick McHardy
2014-04-29 15:23       ` Maxime Bizon
2014-04-29 15:37         ` Eric Dumazet
2014-04-29 20:13           ` Florian Westphal
2014-04-30 14:34           ` Maxime Bizon [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=1398868491.5474.10.camel@sakura.staff.proxad.net \
    --to=mbizon@freebox.fr \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kaber@trash.net \
    --cc=maze@google.com \
    --cc=netdev@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).