Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932177AbcKHSDw (ORCPT ); Tue, 8 Nov 2016 13:03:52 -0500 Received: from mail-sn1nam01on0112.outbound.protection.outlook.com ([104.47.32.112]:54489 "EHLO NAM01-SN1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752430AbcKHSDv (ORCPT ); Tue, 8 Nov 2016 13:03:51 -0500 From: Stephen Hemminger To: KY Srinivasan , "gregkh@linuxfoundation.org" , "linux-kernel@vger.kernel.org" , "devel@linuxdriverproject.org" , "olaf@aepfle.de" , "apw@canonical.com" , "vkuznets@redhat.com" , "jasowang@redhat.com" , "leann.ogasawara@canonical.com" Subject: RE: [PATCH V3 13/14] Drivers: hv: vmbus: On write cleanup the logic to interrupt the host Thread-Topic: [PATCH V3 13/14] Drivers: hv: vmbus: On write cleanup the logic to interrupt the host Thread-Index: AQHSOGLrQZ/OrTcMi0y5C5KUcGTwpaDPWpQw Date: Tue, 8 Nov 2016 17:31:18 +0000 Message-ID: References: <1478466784-32113-1-git-send-email-kys@exchange.microsoft.com> <1478466858-32153-1-git-send-email-kys@exchange.microsoft.com> <1478466858-32153-13-git-send-email-kys@exchange.microsoft.com> In-Reply-To: <1478466858-32153-13-git-send-email-kys@exchange.microsoft.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=sthemmin@microsoft.com; x-originating-ip: [67.189.61.219] x-ms-office365-filtering-correlation-id: 3a487d7c-2f8e-478f-d211-08d407fd0cb0 x-microsoft-exchange-diagnostics: 1;DM5PR03MB2491;7:DgPOxaFY23UZi4Wn1R944L8NrTZ36tByQ5psVV5fHPAiaTGqXfAcrwfk2g2uN1BC4gHYA4Osy41sczf+S5sn191V76K+8nL24nJtjYndYtbWhEs9JRJ+BfQaRKOU5JA4c5pAs2WQ99lixEu8lE/2ROxJ86BPVMcHA5NtUdFJyX5yUS3AV2G5gh87Pm7YheM513lqDUiTs9ptT0lS8YFYC4PzsMXb9OBX4PQFOTH8E84yXEE2b6LHy+jY/KwQfCyJ5uLckecYG+oAcbxyTjxFppvbHwcyJc9DkbJdpISHzq6Fb8yF/Q/D2qrrHZRulB8vIOwzbviOxMxmM3bNTQ1xg0CcHMwY/IQn38jAJ/wfa4h/yx0z1aW2nE3lS0eRolmP x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM5PR03MB2491; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(61425038)(6045074)(6040176)(6060229)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6055026)(61426038)(61427038)(6061226)(6046074);SRVR:DM5PR03MB2491;BCL:0;PCL:0;RULEID:;SRVR:DM5PR03MB2491; x-forefront-prvs: 01208B1E18 x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(6009001)(7916002)(189002)(199003)(3280700002)(3846002)(3660700001)(189998001)(586003)(107886002)(2421001)(92566002)(87936001)(77096005)(97736004)(5001770100001)(102836003)(6116002)(2561002)(8990500004)(99286002)(2906002)(105586002)(106116001)(76576001)(106356001)(2501003)(81166006)(2201001)(81156014)(122556002)(86362001)(8936002)(10090500001)(2950100002)(10290500002)(1511001)(7696004)(5005710100001)(101416001)(7846002)(7736002)(305945005)(86612001)(66066001)(76176999)(54356999)(33656002)(50986999)(68736007)(2900100001)(5660300001)(8676002)(74316002)(9686002);DIR:OUT;SFP:1102;SCL:1;SRVR:DM5PR03MB2491;H:BLUPR0301MB2098.namprd03.prod.outlook.com;FPR:;SPF:None;PTR:InfoNoRecords;MX:1;A:1;LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Nov 2016 17:31:18.5396 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR03MB2491 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id uA8I3uVV009553 Content-Length: 660 Lines: 19 Please don't add name/date information into comments. This kind of meta data belongs in the commit message only. My philosophy is that comments should be reserved for explain the semantics of the code, not the history. + * + * KYS: Oct. 30, 2016: + * It looks like Windows hosts have logic to deal with DOS attacks that + * can be triggered if it receives interrupts when it is not expecting + * the interrupt. The host expects interrupts only when the ring + * transitions from empty to non-empty (or full to non full on the + guest + * to host ring). + * So, base the signaling decision solely on the ring state until the + * host logic is fixed. */