netdev - Re: [PATCH v3 1/4] ipv4: add option to drop unicast encapsulated in L2 multicast

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 28 Jan 2016 16:16:57 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	johannes@...solutions.net
Cc:	ja@....bg, linux-wireless@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH v3 1/4] ipv4: add option to drop unicast encapsulated
 in L2 multicast

From: Johannes Berg <johannes@...solutions.net>
Date: Thu, 28 Jan 2016 13:33:33 +0100

> Is there anything I should do about these patches?
> 
> I see you marked them as "deferred" in patchwork, but I don't really
> know how you're using that state.

I use it in two situations, the first is the most often used case but
doesn't apply to this specific situation :-)

1) net-next change submitted while net-next is closed

2) discussion has ensued for several days, no resolution imminent

And I think #2 is the case that happened here.

You can submit them again to reignite the conversation if you
like.