From: jamal <hadi@cyberus.ca>
To: Eduardo Panisset <eduardo.panisset@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
hideaki@yoshifuji.org, netdev@vger.kernel.org,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Bugme-new] [Bug 15682] New: XFRM is not updating RTAX_ADVMSS metric
Date: Wed, 07 Apr 2010 08:19:11 -0400 [thread overview]
Message-ID: <1270642751.7198.17.camel@bigi> (raw)
In-Reply-To: <y2jb7b22e81004061202uac6ef8eeodc70d6deb65f7699@mail.gmail.com>
Hi Eduardo,
As a first step, I dont know what the real cause is but
what you showed as a solution didnt look right. I am also not familiar
with DSMIPv6. I know a lot of other xfrm subsystems work fine with
the current code. So thats why i pointed to Herbert who is more
knowledgeable. I am adding Yoshfuji to the list.
If you tell me what kernel options to turn on and a very
basic test setup to reproduce it (I dont have much hardware, so make it
very minimal maybe requiring one or two PCs max) then I could make time
and try to reproduce it.
cheers,
jamal
On Tue, 2010-04-06 at 16:02 -0300, Eduardo Panisset wrote:
> Hi,
>
> My intention is only to report a problem that I have faced. The
> solution proposed isn't (I know that) probably the best one to adopt
> as I'm not a kernel specialist, it is more illustrative to allow you
> guys understanding what I'm meaning and solve that on the better way
> (hence I haven't submited a patch).
>
> Regards,
> Eduardo Panisset.
next prev parent reply other threads:[~2010-04-07 12:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15682-10286@https.bugzilla.kernel.org/>
2010-04-05 19:50 ` [Bugme-new] [Bug 15682] New: XFRM is not updating RTAX_ADVMSS metric Andrew Morton
2010-04-06 13:40 ` jamal
2010-04-06 19:02 ` Eduardo Panisset
2010-04-07 12:19 ` jamal [this message]
2010-04-07 13:54 ` Herbert Xu
2010-04-07 23:47 ` David Miller
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=1270642751.7198.17.camel@bigi \
--to=hadi@cyberus.ca \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=davem@davemloft.net \
--cc=eduardo.panisset@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=hideaki@yoshifuji.org \
--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).