netdev - Re: [PATCH net-next] vlan: avoid a synchronize

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAO7SqHA19qRPVO5knye3NE7WJXt7kSY-bvNaosaD40ZBCzaJFA@mail.gmail.com>
Date:	Wed, 11 Mar 2015 15:02:44 -0700
From:	Salam Noureddine <noureddine@...sta.com>
To:	David Miller <davem@...hat.com>
Cc:	Patrick McHardy <kaber@...sh.net>, eric.dumazet@...il.com,
	netdev@...r.kernel.org
Subject: Re: [PATCH net-next] vlan: avoid a synchronize_net when parent device
 goes down

I tested your proposed patch and it seems to work as expected. Thanks!

On Mon, Mar 9, 2015 at 1:54 PM, Salam Noureddine <noureddine@...sta.com> wrote:
> I will run your patch on one of our systems for a day or two and get
> back to you.
>
> On Mon, Mar 9, 2015 at 12:22 PM, David Miller <davem@...hat.com> wrote:
>> From: Salam Noureddine <noureddine@...sta.com>
>> Date: Mon, 9 Mar 2015 12:00:31 -0700
>>
>>> Thanks for pointing to the right direction. Is there a reason the vlan
>>> driver was calling
>>> dev_change_flags instead of dev_close to close the vlan device?
>>
>> Perhaps dev_close() was not exported at the time the code was written,
>> I honestly have no idea.
--
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