Up to [cvs.NetBSD.org] / src / sys / fs / msdosfs
Request diff between arbitrary revisions
Default branch: MAIN
Current tag: netbsd-6
Revision 1.93.6.5 / (download) - annotate - [select for diffs], Tue Oct 17 15:43:09 2017 UTC (6 years, 5 months ago) by martin
Branch: netbsd-6
Changes since 1.93.6.4: +6 -6
lines
Diff to previous 1.93.6.4 (colored) to branchpoint 1.93 (colored) next main 1.94 (colored)
Apply patch form mlelstv to fix the build after pullup #1506
Revision 1.93.6.4 / (download) - annotate - [select for diffs], Fri Oct 13 08:05:30 2017 UTC (6 years, 5 months ago) by snj
Branch: netbsd-6
Changes since 1.93.6.3: +35 -6
lines
Diff to previous 1.93.6.3 (colored) to branchpoint 1.93 (colored)
Pull up following revision(s) (requested by mlelstv in ticket #1506): sys/fs/msdosfs/msdosfs_vfsops.c: revision 1.128 Add more sanity checks for BPB parameters. Handle FAT12 format for media with sectors >= 32kByte. Does fix PR 52485.
Revision 1.93.6.3 / (download) - annotate - [select for diffs], Sun Nov 9 06:37:00 2014 UTC (9 years, 4 months ago) by msaitoh
Branch: netbsd-6
Changes since 1.93.6.2: +50 -41
lines
Diff to previous 1.93.6.2 (colored) to branchpoint 1.93 (colored)
Pull up following revision(s) (requested by maxv in ticket #1171): sys/fs/msdosfs/msdosfs_vfsops.c: revision 1.110 via patch - From me, FreeBSD, OpenBSD and the FAT specification. Ok christos@ - Perform sanity checks not just for GEMDOSFS, but for all FAT devices. This also fixes a division-by-zero bug that could crash the system. - Define GEMDOSFS_BSIZE instead of a hard-coded 512 value, and remove 'bsize'. - Rename 'tmp' to 'BlkPerSec'. - Remove 'secsize==0' and added 'secsize<DEV_BSIZE'
Revision 1.93.6.2 / (download) - annotate - [select for diffs], Mon Apr 21 10:14:19 2014 UTC (9 years, 11 months ago) by bouyer
Branch: netbsd-6
Changes since 1.93.6.1: +4 -2
lines
Diff to previous 1.93.6.1 (colored) to branchpoint 1.93 (colored)
Pull up following revision(s) (requested by maxv in ticket #1050): sys/ufs/chfs/chfs_vfsops.c: revision 1.11 sys/fs/unionfs/unionfs_vfsops.c: revision 1.13 sys/fs/nilfs/nilfs_vfsops.c: revision 1.16 sys/ufs/mfs/mfs_vfsops.c: revision 1.107 sys/fs/sysvbfs/sysvbfs_vfsops.c: revision 1.43 sys/ufs/ffs/ffs_vfsops.c: revision 1.297 sys/kern/vfs_syscalls.c: revision 1.478 sys/kern/vfs_syscalls.c: revision 1.479 sys/fs/puffs/puffs_vfsops.c: revision 1.110 sys/fs/cd9660/cd9660_vfsops.c: revision 1.84 sys/nfs/nfs_vfsops.c: revision 1.227 sys/fs/v7fs/v7fs_vfsops.c: revision 1.10 sys/ufs/ext2fs/ext2fs_vfsops.c: revision 1.180 sys/miscfs/umapfs/umap_vfsops.c: revision 1.92 sys/fs/filecorefs/filecore_vfsops.c: revision 1.76 sys/miscfs/nullfs/null_vfsops.c: revision 1.88 sys/fs/ptyfs/ptyfs_vfsops.c: revision 1.50 sys/coda/coda_vfsops.c: revision 1.81 sys/ufs/lfs/lfs_vfsops.c: revision 1.321 sys/fs/tmpfs/tmpfs_vfsops.c: revision 1.59 sys/fs/hfs/hfs_vfsops.c: revision 1.31 sys/miscfs/overlay/overlay_vfsops.c: revision 1.61 sys/fs/union/union_vfsops.c: revision 1.72 sys/fs/ntfs/ntfs_vfsops.c: revision 1.94 sys/kern/vfs_syscalls.c: revision 1.480 sys/fs/efs/efs_vfsops.c: revision 1.25 sys/kern/vfs_syscalls.c: revision 1.482 sys/fs/msdosfs/msdosfs_vfsops.c: revision 1.107 external/cddl/osnet/dist/uts/common/fs/zfs/zfs_vfsops.c: revision 1.12 sys/miscfs/procfs/procfs_vfsops.c: revision 1.91 sys/fs/smbfs/smbfs_vfsops.c: revision 1.100 sys/fs/adosfs/advfsops.c: revision 1.70 sys/fs/udf/udf_vfsops.c: revision 1.67 Limit check for 'data_len'. Otherwise a (un)privileged user can easily panic the system by passing a huge size. ok christos@ An (un)privileged user can easily make the kernel dereference a NULL pointer. The kernel allows 'data' to be NULL; it's the fs's responsibility to ensure that it isn't NULL (if the fs actually needs data). ok christos@ Some fs's - like kernfs - set their vfs_min_mount_data to zero. Add a check to prevent an (un)privileged user from requesting a zero-sized allocation (and thus a panic). This thing is totally buggy: 'data_len' is modified by the fs, so calling kmem_free with it while its value has changed since the kmem_alloc is far from being a good idea. If the kernel figures out that something mismatches, it will panic (typically with kernfs).
Revision 1.93.6.1 / (download) - annotate - [select for diffs], Thu Jul 5 17:36:31 2012 UTC (11 years, 8 months ago) by riz
Branch: netbsd-6
CVS Tags: netbsd-6-1-RELEASE,
netbsd-6-1-RC4,
netbsd-6-1-RC3,
netbsd-6-1-RC2,
netbsd-6-1-RC1,
netbsd-6-1-4-RELEASE,
netbsd-6-1-3-RELEASE,
netbsd-6-1-2-RELEASE,
netbsd-6-1-1-RELEASE,
netbsd-6-0-RELEASE,
netbsd-6-0-RC2,
netbsd-6-0-RC1,
netbsd-6-0-5-RELEASE,
netbsd-6-0-4-RELEASE,
netbsd-6-0-3-RELEASE,
netbsd-6-0-2-RELEASE,
netbsd-6-0-1-RELEASE,
matt-nb6-plus-nbase,
matt-nb6-plus-base,
matt-nb6-plus
Branch point for: netbsd-6-1,
netbsd-6-0
Changes since 1.93: +3 -3
lines
Diff to previous 1.93 (colored)
Pull up following revision(s) (requested by tsutsui in ticket #395): sys/fs/msdosfs/msdosfs_vfsops.c: revision 1.95 sys/arch/atari/atari/autoconf.c: revision 1.62 sys/dev/md.c: revision 1.67 Add a dirty hack for atari's ancient installation ramdisk: Forcibly configure md0, md1, and md2 devices before setroot() for atari's traditional "auto-load from floppy on open" md_root device which loads installation ramdisk image from floppy. md(4) has been changed dynamically configured at first open after 5.0 and md devices won't appear in "root device:" prompt without this hack. Tested on TT030. Should be pulled up to netbsd-6. Make sure that disklabel of md(4) device is initialized in the case where it's configured in MD md_open_hook(). Without this, msdosfs_mountfs() (which is called from msdosfs_mountroot()) will be called with uninitialized disklabel (d_secsize == 0) and it gets "panic: buf mem pool index 23" later on atari. This is because getdisksize() doesn't check returned d_secsize value and msdosfs_mountfs() blindly calls bread(9) with size==0 in that case. Should be pulled up to netbsd-6 (at least for atari). Add a sanity check if secsize returned from getdisksize() isn't bogus. This prevent possible panic "panic: buf mem pool index 23" later in vfs_bio.c:buf_mempoolidx(). (I'm not sure if it's okay for getdisksize() to assume that partinfo taken from DIOCGPART is properly initialized on all disk(9) devices or not) See also: http://mail-index.NetBSD.org/source-changes/2012/06/30/msg035298.html
Revision 1.93 / (download) - annotate - [select for diffs], Mon Nov 14 18:35:13 2011 UTC (12 years, 4 months ago) by hannken
Branch: MAIN
CVS Tags: netbsd-6-base,
jmcneill-usbmp-pre-base2,
jmcneill-usbmp-base7,
jmcneill-usbmp-base6,
jmcneill-usbmp-base5,
jmcneill-usbmp-base4,
jmcneill-usbmp-base3,
jmcneill-usbmp-base2,
jmcneill-usbmp-base,
jmcneill-audiomp3-base,
jmcneill-audiomp3
Branch point for: netbsd-6,
jmcneill-usbmp
Changes since 1.92: +4 -2
lines
Diff to previous 1.92 (colored)
VOP_OPEN() needs a locked vnode. All these copy-and-pasted xxxfs_mount() implementations need more review.