netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "tung quang nguyen" <tung.q.nguyen@dektech.com.au>
To: "'David Miller'" <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <tipc-discussion@lists.sourceforge.net>
Subject: RE: [tipc-discussion][net v2 1/1] tipc: fix race condition causing hung sendto
Date: Thu, 21 Feb 2019 11:04:46 +0700	[thread overview]
Message-ID: <00af01d4c99a$97324e30$c596ea90$@dektech.com.au> (raw)
In-Reply-To: <20190220.195104.1394349830331192977.davem@davemloft.net>

Hi David,

I compiled previous version and tested it. But I forgot to observe kernel
warning.

For the way to reproduce the issue: calling sendto() and printf() right
after that to print out a log to see if sendto() was successful. On some
occasions, the log was never printed and stack trace showed sendto() was not
returned.
By applying the patch, the issue disappeared.

Thanks.

Best regards,
Tung Nguyen

-----Original Message-----
From: David Miller <davem@davemloft.net> 
Sent: Thursday, February 21, 2019 10:51 AM
To: tung.q.nguyen@dektech.com.au
Cc: netdev@vger.kernel.org; tipc-discussion@lists.sourceforge.net
Subject: Re: [tipc-discussion][net v2 1/1] tipc: fix race condition causing
hung sendto


So if the previous version didn't even compile, I have to ask.

How did you test this?


  reply	other threads:[~2019-02-21  4:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19  7:03 [tipc-discussion][net 0/1] tipc: fix race condition between sleep/wakeup Tung Nguyen
2019-02-19  7:03 ` [tipc-discussion][net 1/1] tipc: fix race condition causing hung sendto Tung Nguyen
2019-02-19 21:21   ` David Miller
2019-02-21  3:31   ` [tipc-discussion][net v2 " Tung Nguyen
2019-02-21  3:51     ` David Miller
2019-02-21  4:04       ` tung quang nguyen [this message]
2019-02-22 23:24     ` David Miller
2019-02-25  3:57     ` [net v3 " Tung Nguyen
2019-02-26 22:52       ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='00af01d4c99a$97324e30$c596ea90$@dektech.com.au' \
    --to=tung.q.nguyen@dektech.com.au \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).