From: Eric Sandeen <sandeen@redhat.com>
To: Jouko Orava <jouko.orava@iki.fi>
Cc: Jouko Orava <jouko.orava@helsinki.fi>,
linux-ext4@vger.kernel.org, Zheng Liu <gnehzuil.liu@gmail.com>
Subject: Re: Bug: Large writes can fail on ext4 if the write buffer is not empty
Date: Thu, 19 Apr 2012 09:45:05 -0500 [thread overview]
Message-ID: <4F9024F1.3000806@redhat.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1204191731340.17249@ruuvi.it.helsinki.fi>
On 4/19/12 9:38 AM, Jouko Orava wrote:
>> FWIW, we tried fairly hard to get the limit lifted in the vfs, to no avail.
>
> I understand. The downsides from the limit are very small, after all.
>
> Has anyone tested the older stable kernel releases?
> When was the VFS limit added, or is it something RHEL kernels patch out?
No, RHEL kernels have the same limits.
>> Agreed, I think Dave was a little to quick on the draw on his reply.
>
> It is easy to miss, the EFAULT on the syscall that follows is so obvious.
>
> I've filed a terse report to the Red Hat Bugzilla:
> https://bugzilla.redhat.com/show_bug.cgi?id=814296
Whoops, I just filed one as well. I'll dup yours to mine since I've already
started the process there.
Thanks,
-Eric
> Let me know if you wish me to expand on that report.
>
> Best regards,
> Jouko Orava
next prev parent reply other threads:[~2012-04-19 14:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 14:47 Bug: Large writes can fail on ext4 if the write buffer is not empty Jouni Siren
2012-04-12 16:06 ` Zheng Liu
2012-04-12 20:20 ` Jan Kara
2012-04-13 1:22 ` [PATCH RESEND] ext4: change return value from int to ssize_t in ext4_file_write Zheng Liu
2012-05-22 19:44 ` Eric Sandeen
2012-05-28 22:08 ` Ted Ts'o
2012-04-13 0:10 ` Bug: Large writes can fail on ext4 if the write buffer is not empty Dave Chinner
2012-04-19 13:10 ` Jouko Orava
2012-04-19 14:15 ` Eric Sandeen
2012-04-19 14:38 ` Jouko Orava
2012-04-19 14:45 ` Eric Sandeen [this message]
2012-04-19 15:09 ` Jouko Orava
2012-04-19 15:28 ` Zheng Liu
2012-04-20 2:12 ` Dave Chinner
2012-04-19 14:56 ` Zheng Liu
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=4F9024F1.3000806@redhat.com \
--to=sandeen@redhat.com \
--cc=gnehzuil.liu@gmail.com \
--cc=jouko.orava@helsinki.fi \
--cc=jouko.orava@iki.fi \
--cc=linux-ext4@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).