From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] bug fix for the ntfs driver
Date: Sat, 10 Nov 2007 18:31:09 +0100 [thread overview]
Message-ID: <87mytmdn36.fsf@xs4all.nl> (raw)
In-Reply-To: <ca0f59980708201921x49d2be2du10f5eaa2ed783a6b@mail.gmail.com> (bean123ch@gmail.com's message of "Tue, 21 Aug 2007 10:21:03 +0800")
Bean <bean123ch@gmail.com> writes:
Hi,
> The problem is caused by the structure of compressed files. In ntfs,
> 16 clusters is the basic compressed unit. The original code assume
> that the file will break in 16 cluster long blocks, but in fact, the
> blocks will be merged if they are stored next to to each other on
> disk. The new code fix this problem.
>
> * fs/ntfs.c (read_block): Fix a bug caused by adjacent blocks.
Sorry for forgetting about this patch. It should be committed.
Robert, if you have time, can you commit this? I will mark this mail
as important... If you don't have the time, I will surely commit it
ASAP :-)
--
Marco
next prev parent reply other threads:[~2007-11-10 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 16:26 [PATCH] bug fix for the ntfs driver Bean
2007-08-20 14:04 ` Marco Gerards
2007-08-21 2:21 ` Bean
2007-11-10 17:31 ` Marco Gerards [this message]
2007-11-10 20:08 ` Robert Millan
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=87mytmdn36.fsf@xs4all.nl \
--to=mgerards@xs4all.nl \
--cc=grub-devel@gnu.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 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.