netdev - Re: [PATCH 0/4] l2tp: fix namespace support in l2tp

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:	Tue, 05 Feb 2013 13:56:53 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	tparkin@...alix.com
Cc:	netdev@...r.kernel.org, jchapman@...alix.com, celston@...alix.com
Subject: Re: [PATCH 0/4] l2tp: fix namespace support in l2tp_core

From: Tom Parkin <tparkin@...alix.com>
Date: Tue, 5 Feb 2013 09:27:09 +0000

> On Mon, Feb 04, 2013 at 01:21:07PM -0500, David Miller wrote:
>> 
>> These patches don't apply cleanly to net-next, please respin.
> 
> Hmm.  I think the problem is that this patchset builds on the bug-fix
> work of this previous submission:
> 
>   * l2tp: prevent l2tp_tunnel_delete racing with userspace close
> 
> The bug fix patch went to the net tree, not net-next, hence the
> problem.  I should have made the dependency between the two patches
> more explicit -- apologies for not having done so!
> 
> What's the right thing for me to do in a situation like this?  Should
> I wait and resubmit when net-next and net are next synchronised?

The best thing to do is tell me about the dependency, then I can
pull 'net' into 'net-next' before applying your patches.

I'll do that right now.
--
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