From: James D Strandboge <jstrand1@rochester.rr.com>
To: linux-kernel@vger.kernel.org
Subject: fat problem in 2.4.2
Date: Sun, 25 Feb 2001 15:08:36 -0500 [thread overview]
Message-ID: <3A996644.A5856F14@rochester.rr.com> (raw)
The bug with truncate in the fat filesystem that was present in 2.4.0,
and fixed with the 2.4.0-ac12 (or earlier) patch is still in the main
(unpatched) kernel, both 2.4.1 and 2.4.2. The problem is that I cannot
apply the 2.4.0-ac patch to the newer kernels and I cannot patch up to
2.4.1 from 2.4.0 if I already applied the ac patch (so I obviously can't
get to 2.4.2). I also can't patch from 2.4.0-ac12 to 2.4.1-ac20 using
only ac patches. Neither of the ac patches for 2.4.1 and 2.4.2 have
this fix for fat, so giving the '-R' option to patch took away the fix.
I would be happy to extract the fix from 2.4.0-ac12, but I am not a
kernel developer and am not sure how many files were changed to fix this
bug.
I want to move up to 2.4.2 for the reiserfs updates and then eventually
to at least 2.4.2-ac2 for the loopback fix (but need the fat
functionality too).
Thanks for any help or suggestions.
James Strandboge
jstrand1@rochester.rr.com
next reply other threads:[~2001-02-25 20:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 20:08 James D Strandboge [this message]
2001-02-25 20:20 ` fat problem in 2.4.2 Alan Cox
2001-03-01 14:25 ` Peter Daum
2001-03-01 15:09 ` [PATCH] " Alexander Viro
2001-03-02 0:21 ` Albert D. Cahalan
2001-03-01 18:19 ` Alan Cox
2001-03-01 19:39 ` [CFT][PATCH] " Alexander Viro
2001-03-01 20:05 ` Linus Torvalds
2001-03-01 20:52 ` Chris Mason
2001-03-01 20:56 ` Roman Zippel
2001-03-01 21:07 ` Alexander Viro
2001-03-01 21:27 ` Roman Zippel
2001-03-02 7:45 ` ftruncate not extending files? bert hubert
2001-03-02 9:57 ` Malcolm Beattie
2001-03-02 10:56 ` Dmitry A. Fedorov
2001-03-02 14:15 ` Hugh Dickins
2001-03-03 19:32 ` Kai Henningsen
[not found] ` <mng==20010302095701.A4685@sable.ox.ac.uk>
2001-03-02 23:41 ` Jens-Uwe Mager
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=3A996644.A5856F14@rochester.rr.com \
--to=jstrand1@rochester.rr.com \
--cc=linux-kernel@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 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.