linux-kernel - [PATCH v5] Block backend checks for insane ring entries.

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: <1370880106-7606-1-git-send-email-konrad.wilk@oracle.com>
Date:	Mon, 10 Jun 2013 12:01:44 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	linux-kernel@...r.kernel.org, xen-devel@...ts.xensource.com
Subject: [PATCH v5] Block backend checks for insane ring entries.

These patches were posted in the past (v2?) and at which point Jan
Beulich suggested to use a different macro. Unfortunatly after a
more exhaustive testing it was found that said macro is not
appropiate and would needlessly hang up the connection.

Hence re-introducing the new macro which will allow to detect
the producer and consumer indexes being greater than the ring size:

 [v5 1/2] xen/ring: Add a new macro to detect whether there is an

And the patch which will now use it:
 [v5 2/2] xen/blkback: Check for insane amounts of request on the ring

 drivers/block/xen-blkback/blkback.c | 12 +++++++++++-
 drivers/block/xen-blkback/common.h  |  2 ++
 drivers/block/xen-blkback/xenbus.c  |  2 ++
 include/xen/interface/io/ring.h     |  6 ++++++
 4 files changed, 21 insertions(+), 1 deletion(-)

Konrad Rzeszutek Wilk (2):
      xen/ring: Add a new macro to detect whether there is an overflow in requests and response.
      xen/blkback: Check for insane amounts of request on the ring (v5).

--
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/