From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Jouko Orava <jouko.orava@helsinki.fi>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: Bug: Large writes can fail on ext4 if the write buffer is not empty
Date: Thu, 19 Apr 2012 23:28:36 +0800 [thread overview]
Message-ID: <CANWLp02j-S8rcDHCMXRveY8ypo2vxy6306iC=zP-gVPLFVjtxw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1204191803360.19837@ruuvi.it.helsinki.fi>
On Thu, Apr 19, 2012 at 11:09 PM, Jouko Orava <jouko.orava@helsinki.fi> wrote:
>> No, RHEL kernels have the same limits.
>
> That means at least 2.6.32.x stable series will suffer from the same bug.
> I'll see if I can test those mainline kernels too this weekend.
Great! Please test it in stable kernels because I am afraid that I
couldn't do this work at this weekend. :-)
Regards,
Zheng
>
>> Whoops, I just filed one as well. I'll dup yours to mine since I've already
>> started the process there.
>
> That's excellent, thank you. Mine was unacceptably terse anyway :)
>
> Thanks,
> Jouko
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-04-19 15:28 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
2012-04-19 15:09 ` Jouko Orava
2012-04-19 15:28 ` Zheng Liu [this message]
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='CANWLp02j-S8rcDHCMXRveY8ypo2vxy6306iC=zP-gVPLFVjtxw@mail.gmail.com' \
--to=gnehzuil.liu@gmail.com \
--cc=jouko.orava@helsinki.fi \
--cc=linux-ext4@vger.kernel.org \
--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.