[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110118211450.GC4288@del.dom.local>
Date: Tue, 18 Jan 2011 22:14:50 +0100
From: Jarek Poplawski <jarkao2@...il.com>
To: Pablo Neira Ayuso <pablo@...filter.org>
Cc: David Miller <davem@...emloft.net>, arthur.marsh@...ernode.on.net,
jengelh@...ozas.de, eric.dumazet@...il.com, netdev@...r.kernel.org,
hadi@...erus.ca
Subject: Re: inbound connection problems when "netlink: test for all flags
of the NLM_F_DUMP composite" commit applied
On Tue, Jan 18, 2011 at 09:31:31PM +0100, Pablo Neira Ayuso wrote:
> On 18/01/11 11:24, Jarek Poplawski wrote:
> > On Tue, Jan 18, 2011 at 02:07:02AM -0800, David Miller wrote:
> >> From: Jarek Poplawski <jarkao2@...il.com>
> >> Date: Tue, 18 Jan 2011 09:38:11 +0000
> >>
> >>> Even if I'm wrong, this change added to stable will break many configs.
> >>> My proposal is to revert commit 0ab03c2b147 until proper fix is found.
> >>
> >> The flag combination is, at best ambiguous, it has no proper
> >> definition without the check we added.
> >
> > Do you all expect all users manage to upgrade avahi app before
> > changing their stable kernel? I mean "own distro" users especially.
>
> The combination that avahi uses makes no sense.
>
> I've been auditing user-space tools that may have problems with this change:
>
> * iw (it uses libnl)
> * acpid (it uses a mangled version of libnetlink shipped in iproute)
> * tstime, for taskstats, it uses libnl
> * wimax-tools, it uses libnl
> * quota-tools, it uses libnl
> * keepalived, no libs used
>
> Well, I can keep looking for more, but I think that avahi is the only
> one doing this incorrectly.
BTW, could you answer my earlier question, why NLM_F_ATOMIC flag isn't
handled now with dumps?
Jarek P.
--
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
Powered by blists - more mailing lists