From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51845) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XCUx7-0003p3-Ao for Qemu-devel@nongnu.org; Wed, 30 Jul 2014 10:34:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XCUww-0000rN-HV for Qemu-devel@nongnu.org; Wed, 30 Jul 2014 10:34:01 -0400 Received: from isrv.corpit.ru ([86.62.121.231]:43115) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XCUww-0000fm-AV for Qemu-devel@nongnu.org; Wed, 30 Jul 2014 10:33:50 -0400 Message-ID: <53D90245.2050903@msgid.tls.msk.ru> Date: Wed, 30 Jul 2014 18:33:41 +0400 From: Michael Tokarev MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] 9p mapped-* security model infos are architecture-specific List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Qemu Development List Cc: "Aneesh Kumar K.V" Apparently the the mapped-* security models results in a raw bytes being dumped to host without any architecture normalization (in host byte order). This may even lead to security issues in guest when the same files are served from another host for example. This bug has been initially submitted against debian qemu package, see http://bugs.debian.org/755740 Thanks, /mjt