linux-kernel - [patch 0/2][RFC] vfs: artefact(?) in rw_verify

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

Message-ID: <4CB61A7F.9070603@redhat.com>
Date:	Wed, 13 Oct 2010 22:45:51 +0200
From:	Edward Shishkin <edward@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-fsdevel@...r.kernel.org
CC:	Eric Sandeen <sandeen@...hat.com>, lmcilroy@...hat.com,
	LKML <linux-kernel@...r.kernel.org>
Subject: [patch 0/2][RFC] vfs: artefact(?) in rw_verify_area

Hello everyone.

rw_verify_area() contains a limitation, which means inability
to write more then INT_MAX bytes atomically. This tends
to be a disadvantage since INT_MAX doesn't look like a huge
value nowadays. Moreover, this restriction looks too artificial.

I have increased the limit up to rounded down SSIZE_MAX
(patch 2) and got an overflow in the direct-io subsystem.
However, after fixing the overflow (patch 1), ext3,4 work
fine for me so far.

Any ideas, if there are other subsystems that expose the
INT_MAX limitation?

Thanks in advance,

-- 
Edward O. Shishkin
Principal Software Engineer
Red Hat Czech

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