All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>, linux-fsdevel@vger.kernel.org
Cc: Eric Sandeen <sandeen@redhat.com>,
	lmcilroy@redhat.com, LKML <linux-kernel@vger.kernel.org>
Subject: [patch 0/2][RFC] vfs: artefact(?) in rw_verify_area
Date: Wed, 13 Oct 2010 22:45:51 +0200	[thread overview]
Message-ID: <4CB61A7F.9070603@redhat.com> (raw)

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


                 reply	other threads:[~2010-10-13 20:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CB61A7F.9070603@redhat.com \
    --to=edward@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lmcilroy@redhat.com \
    --cc=sandeen@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.