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]
Date:	Wed, 13 Aug 2014 14:59:18 -0700
From:	Raghuram Kothakota <>
To:	Sowmini Varadhan <>
Cc:	David Miller <>,
Subject: Re: [PATCH net-next 3/3] sunvnet: Schedule maybe_tx_wakeup as a tasklet from ldc_rx path

On Aug 13, 2014, at 3:51 AM, Sowmini Varadhan <> wrote:

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

The reset event is expected for the peer, if it is not happening
then we probably need to check why.

> 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
More majordomo info at

Powered by blists - more mailing lists