From: David Miller <davem@davemloft.net>
To: decui@microsoft.com
Cc: sunilmut@microsoft.com, kys@microsoft.com,
haiyangz@microsoft.com, sthemmin@microsoft.com,
sashal@kernel.org, mikelley@microsoft.com,
netdev@vger.kernel.org, linux-hyperv@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] hvsock: fix epollout hang from race condition
Date: Sun, 16 Jun 2019 13:54:45 -0700 (PDT) [thread overview]
Message-ID: <20190616.135445.822152500838073831.davem@davemloft.net> (raw)
In-Reply-To: <PU1P153MB0169BACDA500F94910849770BFE90@PU1P153MB0169.APCP153.PROD.OUTLOOK.COM>
From: Dexuan Cui <decui@microsoft.com>
Date: Sat, 15 Jun 2019 03:22:32 +0000
> These warnings are not introduced by this patch from Sunil.
>
> I'm not sure why I didn't notice these warnings before.
> Probably my gcc version is not new eought?
>
> Actually these warnings are bogus, as I checked the related functions,
> which may confuse the compiler's static analysis.
>
> I'm going to make a patch to initialize the pointers to NULL to suppress
> the warnings. My patch will be based on the latest's net.git + this patch
> from Sunil.
Sunil should then resubmit his patch against something that has the
warning suppression patch applied.
next prev parent reply other threads:[~2019-06-16 20:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 21:19 [PATCH net] hvsock: fix epollout hang from race condition Sunil Muthuswamy
2019-06-13 23:35 ` Dexuan Cui
2019-06-15 2:14 ` David Miller
2019-06-15 3:22 ` Dexuan Cui
2019-06-15 5:03 ` Dexuan Cui
2019-06-15 7:23 ` Sunil Muthuswamy
2019-06-15 17:01 ` Dexuan Cui
2019-06-16 20:54 ` David Miller [this message]
2019-06-17 18:47 ` Sunil Muthuswamy
2019-06-17 18:56 ` David Miller
2019-06-17 19:27 ` Sunil Muthuswamy
2019-06-17 20:04 ` 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=20190616.135445.822152500838073831.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=sunilmut@microsoft.com \
/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).