Re: [PATCH][BUG] ext4: fix returning with 0 from write system call on ext4 with noextent

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Toshiyuki Okajima <toshi.okajima@xxxxxxxxxxxxxx>
Subject: Re: [PATCH][BUG] ext4: fix returning with 0 from write system call on ext4 with noextent
From: "Ted Ts'o" <tytso@xxxxxxx>
Date: Tue, 27 Jul 2010 09:53:12 -0400
Cc: adilger@xxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, sandeen@xxxxxxxxxx
In-reply-to: <20100726111636.72264f8c.toshi.okajima@xxxxxxxxxxxxxx>
User-agent: Mutt/1.5.20 (2009-06-14)

Thanks, I've applied this patch, although I edited patch description
to make it be a bit more succint.

				- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

References:
- [PATCH][BUG] ext4: fix returning with 0 from write system call on ext4 with noextent
  - From: Toshiyuki Okajima

Prev by Date: Re: [PATCH] ext4: fix ext4_get_blocks references
Next by Date: Re: [PATCH] ext4: don't print scary messages for allocation failures post-abort
Previous by thread: Re: [PATCH][BUG] ext4: fix returning with 0 from write system call on ext4 with noextent
Next by thread: [PATCH] ext4: don't print scary messages for allocation failures post-abort
Index(es):
- Date
- Thread

[Index of Archives] [Reiser Filesystem Development] [Ceph FS] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite National Park] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper] [Linux Media]

Powered by Linux