linux-kernel - [PATCH 0/2] Drivers: hv: kvp,vss: improve kernel-userspace communication in failure case

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-next>] [day] [month] [year] [list]

Message-Id: <1415294485-23945-1-git-send-email-vkuznets@redhat.com>
Date:	Thu,  6 Nov 2014 18:21:23 +0100
From:	Vitaly Kuznetsov <vkuznets@...hat.com>
To:	"K. Y. Srinivasan" <kys@...rosoft.com>,
	Haiyang Zhang <haiyangz@...rosoft.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	devel@...uxdriverproject.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] Drivers: hv: kvp,vss: improve kernel-userspace communication in failure case

This series addresses two issues:
- There is no timeout when communicating with userspace VSS daemon.
- In case we fail to send a message to VSS or KVP userspace daemons we
  can report the failure to the host right away avoiding the timeout.

Newly introduced 10 second timeout is something worth discussing. In theory freeze/thaw
ioctls should be fast. In case someone thinks 10 seconds is not enough we can easily
increase it as we cover the most common failure scenario (when the daemon was stopped)
with the second patch of this series.

Vitaly Kuznetsov (2):
  Drivers: hv: vss: Introduce timeout for communication with userspace
  Drivers: hv: kvp,vss: Fast propagation of userspace communication
    failure

 drivers/hv/hv_kvp.c      |  9 ++++++++-
 drivers/hv/hv_snapshot.c | 28 +++++++++++++++++++++++++---
 2 files changed, 33 insertions(+), 4 deletions(-)

-- 
1.9.3

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/