linux-kernel - Re: [PATCH net] netconsole: Check for carrier before calling netpoll_send

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: <20150811.102521.448694660627631235.davem@davemloft.net>
Date:	Tue, 11 Aug 2015 10:25:21 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	jmaxwell37@...il.com
Cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	jmaxwell@...hat.com
Subject: Re: [PATCH net] netconsole: Check for carrier before calling
 netpoll_send_udp()

From: Jonathan Maxwell <jmaxwell37@...il.com>
Date: Tue, 11 Aug 2015 15:53:18 +1000

>> What if the carrier check passes, and then the chip reset starts on
>> another cpu?  You'll have the same problem.
> 
> Okay, let me see if I can come up with a better way to mitigate this.

I personally think that drivers need to synchronize such things
internally.  They are the only entity which knows when it's "OK"
to do whatever the netpoll method does, and they are also the only
entity which can properly synchronize such checks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/