All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: David Ahern <dsahern@gmail.com>,
	Ido Schimmel <idosch@mellanox.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH iproute2-next] bridge: fdb: Use 'struct ndmsg' for FDB dumping
Date: Tue, 1 Jan 2019 07:55:49 +0200	[thread overview]
Message-ID: <20190101055549.GA5063@splinter.mtl.com> (raw)
In-Reply-To: <20181231202538.47f58387@shemminger-XPS-13-9360>

On Mon, Dec 31, 2018 at 08:25:38PM -0800, Stephen Hemminger wrote:
> On Sun, 30 Dec 2018 18:03:47 -0700
> David Ahern <dsahern@gmail.com> wrote:
> 
> > On 12/30/18 10:14 AM, Ido Schimmel wrote:
> > > Since commit aea41afcfd6d ("ip bridge: Set NETLINK_GET_STRICT_CHK on
> > > socket") iproute2 uses strict checking on kernels that support it. This
> > > causes FDB dumping to fail [1], as iproute2 uses 'struct ifinfomsg'
> > > whereas the kernel expects 'struct ndmsg'.
> > > 
> > > Note that with this change iproute2 continues to work on old kernels
> > > that do not support strict checking, but contain the fix introduced in
> > > kernel commit bd961c9bc664 ("rtnetlink: fix rtnl_fdb_dump() for ndmsg
> > > header").
> 
> Sorry, I don't think that is good enough backward compatibility guarantee.
> Iproute2 should work on really old kernels like 2.6.32. If not then then iproute2
> utility is broken or the changes to the kernel API were incorrect.

I found two more issues for which I have patches. I tested with and
without strict checking and I'll test on some old kernels as well. No
intention to break backward compatibility. Will Cc you.

Thanks

      reply	other threads:[~2019-01-01  5:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-30 17:14 [PATCH iproute2-next] bridge: fdb: Use 'struct ndmsg' for FDB dumping Ido Schimmel
2018-12-31  1:03 ` David Ahern
2019-01-01  4:25   ` Stephen Hemminger
2019-01-01  5:55     ` Ido Schimmel [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=20190101055549.GA5063@splinter.mtl.com \
    --to=idosch@idosch.org \
    --cc=dsahern@gmail.com \
    --cc=idosch@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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.