netdev - Re: [PATCH net-next 3/3] sunvnet: Schedule maybe_tx_wakeup as a tasklet from ldc

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: <20140813105137.GB16865@oracle.com>
Date:	Wed, 13 Aug 2014 06:51:37 -0400
From:	Sowmini Varadhan <sowmini.varadhan@...cle.com>
To:	Raghuram Kothakota <Raghuram.Kothakota@...cle.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [PATCH net-next 3/3] sunvnet: Schedule maybe_tx_wakeup as a
 tasklet from ldc_rx path

On (08/12/14 21:26), Raghuram Kothakota wrote:
> 
> We do not consider a peer which couldn't process LDC messages
> as an offender but just a peer in a broken state. A peer could get

So I was using "offender" in the same way that one typically
talks about sending  ICMP errors for "offending IP packets" 
(nothing pesonal :-)).  I dont want to quibble over terminology here.
 
> From what I read the ldc_disconect() code, it seems like it is reconfiguring
> the queues, so I assume a reset event would re-enable the communication
> fine, but I don't know for sure without testing this specific condition.

No such events were generated by the code when I tested it.

I'll send a consolidated reply to the rest of that very long thread 
in a bit.

--Sowmini

--
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