On Sun, Apr 22, 2001 at 10:59:18PM -0400, Douglas Gilbert wrote:
> One error report stated that a MO drive with a vfat
> fs based on 2048 byte sectors can be mounted and read
Read? I don't think so. bread, yes, but read follows a NULL pointer and
was never seen again.
> but any significant
> The EIP resolved most often to cont_prepare_write() in
> fs/buffer. A disassembly suggests line 1802 in buffer.c
> [2.4.3ac11]. That is around a memset() between
> __block_prepare_write() and __block_commit_write() calls
> within the while loop. Most other addresses were within
> the same while
The EIP resolved most often to cont_prepare_write() in
fs/buffer. A disassembly suggests line 1802 in buffer.c
[2.4.3ac11]. That is around a memset() between
__block_prepare_write() and __block_commit_write() calls
within the while loop. Most other addresses were within
the same while loop.
On Sun, Apr 22, 2001 at 10:59:18PM -0400, Douglas Gilbert wrote:
One error report stated that a MO drive with a vfat
fs based on 2048 byte sectors can be mounted and read
Read? I don't think so. bread, yes, but read follows a NULL pointer and
was never seen again.
but any significant write
The "MO" bug (also 2048 byte block vfat problem) has been
reported several times in the lk 2.4 series. Since the
finger was being pointed at the SCSI subsystem I decided
to investigate. As far as I can see the sd driver offers
the same physical block (other than 512 byte) capabilities
in lk 2.4
The MO bug (also 2048 byte block vfat problem) has been
reported several times in the lk 2.4 series. Since the
finger was being pointed at the SCSI subsystem I decided
to investigate. As far as I can see the sd driver offers
the same physical block (other than 512 byte) capabilities
in lk 2.4 as
6 matches
Mail list logo
