Re: [PATCH 0/7] fixes for fsck.cramfs and other things

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

 



On Wed, Jan 24, 2018 at 03:47:57PM +0100, Ruediger Meier wrote:
> On Wednesday 24 January 2018, Karel Zak wrote:
> > On Tue, Jan 23, 2018 at 04:59:21PM +0100, Ruediger Meier wrote:
> > > From: Ruediger Meier <ruediger.meier@xxxxxxxxxxx>
> > >
> > > Ruediger Meier (6):
> > >   Revert "fsck.cramfs: Fix bus error on broken file system."
> > >   fsck.cramfs: fix crash when superblock size is too small
> > >   tests: rewrite fsck-bad-header
> >
> > Nice.
> >
> > >   fsck.cramfs: fix error message
> 
> BTW while we are at this. I wonder why we have 3 different ways 
> (fallbacks) in fsck.cramfs.c test_crc() how to read the image.
> 
> 1. mmap
> 2. read into anonymous mmap
> 3. read blockwise
> 
> Does anybody knows why is this and whether we still need all these 
> fallbacks?

The question is why we need mmap at all here;-)

    Karel

-- 
 Karel Zak  <kzak@xxxxxxxxxx>
 http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux