[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181005.145831.572080355383428846.davem@davemloft.net>
Date: Fri, 05 Oct 2018 14:58:31 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: dsahern@...il.com
Cc: mfo@...onical.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next] rtnetlink: fix rtnl_fdb_dump() for shorter
family headers
From: David Ahern <dsahern@...il.com>
Date: Fri, 5 Oct 2018 15:24:29 -0600
> On 10/5/18 3:22 PM, David Miller wrote:
>> From: Mauricio Faria de Oliveira <mfo@...onical.com>
>> Date: Mon, 1 Oct 2018 22:50:32 -0300
>>
>>> On Mon, Oct 1, 2018 at 12:38 PM Mauricio Faria de Oliveira
>>> <mfo@...onical.com> wrote:
>>>> Ok, thanks for your suggestions.
>>>> I'll do some research/learning on them, and give it a try for a v2.
>>>
>>> FYI, that is "[PATCH v2 net-next] rtnetlink: fix rtnl_fdb_dump() for
>>> ndmsg header".
>>>
>>> BTW, could please advise whether this should be net or net-next? It's a bug fix,
>>> but it's late in the cycle, and this is not urgent (the problem has been around
>>> since v4.12), so not sure it's really needed for v4.19.
>>
>> I've applied this to net and queued it up for -stable, thanks.
>>
>
> there was a v2 for this problem. I reviewed it and been testing it as
> part of the strict dump patches.
Oh crap, sorry, please send me a relative fixup :-/
Powered by blists - more mailing lists