History log of /src/sys/fs/udf/udf_vfsops.c |
Revision | | Date | Author | Comments |
1.86 |
| 25-Aug-2025 |
reinoud | Assert that udf_get_node()/udf_loadvnode() returns a valid root node when it doesn't return an error.
|
1.85 |
| 03-May-2022 |
hannken | Lock devvp for vinvalbuf().
|
1.84 |
| 23-Mar-2022 |
andvar | fix few typos for word "previous(ly)" in comments.
|
1.83 |
| 16-Dec-2021 |
reinoud | Make sysctl udf.verbose dependent on UDF_DEBUG instead of DEBUG
|
1.82 |
| 16-Sep-2021 |
andvar | fix typos in word "successful".
|
1.81 |
| 24-Jul-2021 |
andvar | Fix all remaining typos, mainly in comments but also in few definitions and log messages, reported by me in PR kern/54889. Also fixed some additional typos in comments, found on review of same files or typos.
|
1.80 |
| 14-Apr-2020 |
reinoud | branches: 1.80.6; Move comment related to the sysctl_createv() in SYSCTL_SETUP() from the old place to the new place too.
|
1.79 |
| 13-Apr-2020 |
ad | Replace most uses of vp->v_usecount with a call to vrefcnt(vp), a function that hides the details and does atomic_load_relaxed(). Signature matches FreeBSD.
|
1.78 |
| 16-Mar-2020 |
pgoyette | branches: 1.78.2; Use the module subsystem's ability to process SYSCTL_SETUP() entries to automate installation of sysctl nodes.
Note that there are still a number of device and pseudo-device modules that create entries tied to individual device units, rather than to the module itself. These are not changed.
|
1.77 |
| 17-Jan-2020 |
ad | VFS_VGET(), VFS_ROOT(), VFS_FHTOVP(): give them a "int lktype" argument, to allow us to get shared locks (or no lock) on the returned vnode. Matches FreeBSD.
|
1.76 |
| 24-Jun-2017 |
hannken | branches: 1.76.6; 1.76.10; 1.76.12; No need to call vflush from failing udf_mount(). If the system nodes really have to disappear we should change vrele() to vrecycle() here.
|
1.75 |
| 01-Apr-2017 |
riastradh | branches: 1.75.4; 1.75.6; KASSERT(mutex_owned(vp->v_interlock)) in vnode iterator selector.
|
1.74 |
| 17-Feb-2017 |
hannken | Add generic genfs_suspendctl() and use it for all file systems. Layered file systems need work.
|
1.73 |
| 07-Jul-2016 |
msaitoh | branches: 1.73.2; 1.73.4; KNF. Remove extra spaces. No functional change.
|
1.72 |
| 29-Jan-2016 |
christos | It is meaningless to check the root node if there was an error.
|
1.71 |
| 24-Aug-2015 |
hannken | Use vfs_vnode_iterator for udf_do_sync.
- Build rb_tree to get an ordered list of nodes, sync them and clean the tree.
- Stop abusing mntvnode_lock to serialize udf_do_sync, use new mutex ump->sync_lock instead.
|
1.70 |
| 24-Aug-2015 |
hannken | Use vfs_vnode_iterator for udf_unmount_sanity_check.
|
1.69 |
| 24-Aug-2015 |
hannken | Remove dirtynodes_cv, it is only used for timed waits without any signals.
Replace the cv_timedwait with kpause.
|
1.68 |
| 06-Apr-2015 |
hannken | Change udf to vcache, keyed on udf_node->loc.loc.
|
1.67 |
| 16-Apr-2014 |
maxv | branches: 1.67.4; 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@
|
1.66 |
| 23-Mar-2014 |
hannken | branches: 1.66.2; Change all vfsops to use C99 designated initializers.
No functional changes intended.
|
1.65 |
| 25-Feb-2014 |
pooka | Ensure that the top level sysctl nodes (kern, vfs, net, ...) exist before the sysctl link sets are processed, and remove redundancy.
Shaves >13kB off of an amd64 GENERIC, not to mention >1k duplicate lines of code.
|
1.64 |
| 30-Sep-2013 |
hannken | Replace macro v_specmountpoint with two functions spec_node_getmountedfs() and spec_node_setmountedfs() to manage the file system mounted on a device. Assert the device is a block device.
Welcome to 6.99.24
Discussed on tech-kern@ some time ago.
Reviewed by: David Holland <dholland@netbsd.org>
|
1.63 |
| 13-Mar-2012 |
elad | branches: 1.63.2; 1.63.4; Replace the remaining KAUTH_GENERIC_ISSUSER authorization calls with something meaningful. All relevant documentation has been updated or written.
Most of these changes were brought up in the following messages:
http://mail-index.netbsd.org/tech-kern/2012/01/18/msg012490.html http://mail-index.netbsd.org/tech-kern/2012/01/19/msg012502.html http://mail-index.netbsd.org/tech-kern/2012/02/17/msg012728.html
Thanks to christos, manu, njoly, and jmmv for input.
Huge thanks to pgoyette for spinning these changes through some build cycles and ATF.
|
1.62 |
| 14-Nov-2011 |
hannken | branches: 1.62.4; 1.62.6; 1.62.10; 1.62.12; VOP_OPEN() needs a locked vnode. All these copy-and-pasted xxxfs_mount() implementations need more review.
|
1.61 |
| 27-Sep-2011 |
christos | branches: 1.61.2; - rename UDF_MAX_NAMELEN -> UDF_MAXNAMLEN - use NAME_MAX instead of MAXNAMLEN
|
1.60 |
| 24-Jun-2010 |
hannken | Clean up vnode lock operations pass 2:
VOP_UNLOCK(vp, flags) -> VOP_UNLOCK(vp): Remove the unneeded flags argument.
Welcome to 5.99.32.
Discussed on tech-kern.
|
1.59 |
| 07-Jul-2009 |
reinoud | branches: 1.59.2; 1.59.4; Replace the old hashtable and sorted list implemenation by a RB-tree.
Benefits are significant speed improvements on node creation/insertion while keeping the lookup times low and still allowing sequential iteration over the nodes.
|
1.58 |
| 29-Jun-2009 |
dholland | Convert 67 namei call sites to use namei_simple, in these functions:
check_console, veriexecclose, veriexec_delete, veriexec_file_add, emul_find_root, coff_load_shlib (sh3 version), coff_load_shlib, compat_20_sys_statfs, compat_20_netbsd32_statfs, ELFNAME2(netbsd32,probe_noteless), darwin_sys_statfs, ibcs2_sys_statfs, ibcs2_sys_statvfs, linux_sys_uselib, osf1_sys_statfs, sunos_sys_statfs, sunos32_sys_statfs, ultrix_sys_statfs, do_sys_mount, fss_create_files (3 of 4), adosfs_mount, cd9660_mount, coda_ioctl, coda_mount, ext2fs_mount, ffs_mount, filecore_mount, hfs_mount, lfs_mount, msdosfs_mount, ntfs_mount, sysvbfs_mount, udf_mount, union_mount, sys_chflags, sys_lchflags, sys_chmod, sys_lchmod, sys_chown, sys_lchown, sys___posix_chown, sys___posix_lchown, sys_link, do_sys_pstatvfs, sys_quotactl, sys_revoke, sys_truncate, do_sys_utimes, sys_extattrctl, sys_extattr_set_file, sys_extattr_set_link, sys_extattr_get_file, sys_extattr_get_link, sys_extattr_delete_file, sys_extattr_delete_link, sys_extattr_list_file, sys_extattr_list_link, sys_setxattr, sys_lsetxattr, sys_getxattr, sys_lgetxattr, sys_listxattr, sys_llistxattr, sys_removexattr, sys_lremovexattr
All have been scrutinized (several times, in fact) and compile-tested, but not all have been explicitly tested in action.
XXX: While I haven't (intentionally) changed the use or nonuse of XXX: TRYEMULROOT in any of these places, I'm not convinced all the XXX: uses are correct; an audit might be desirable.
|
1.57 |
| 24-Jun-2009 |
reinoud | Commit first stage of free-space accounting. It is estimating the underlimit of free blocks on the device and when free blocks are getting tight it tries to readjust/recalculate that value by syncing the FS.
Second stage will be resizing the data/metadata partitions.
|
1.56 |
| 25-Apr-2009 |
elad | Add genfs_can_mount() and use it to prevent some more code duplication of the security checks when mounting a device (VOP_ACCESS() + kauth(9) call)).
Proposed with no objections on tech-kern@:
http://mail-index.netbsd.org/tech-kern/2009/04/20/msg004859.html
The vnode is always expected to be locked, so no locking is done outside the file-system code.
|
1.55 |
| 08-Feb-2009 |
reinoud | branches: 1.55.2; If mounting for read-write dont allow a session number to be specified since its currently still misbehaving. If supported later, it would allow one or a series of sessions on a sequential recordable media to be ignored as if they never were created.
Also fix a small comment: its not the direct but the bootstrap disc strategy that we close down.
|
1.54 |
| 16-Dec-2008 |
reinoud | Check for a node being root on node creation so when the root node is disposed of when working deep into the directory tree it can reliably be reget and marked correctly as the FS root.
Fixed pwd(1) lock panic and possible endless loop in other tools.
|
1.53 |
| 16-Dec-2008 |
pooka | The great QUOTA purge of '08: get rid of those #ifdef QUOTA and #include "opt_quota.h" which do exactly nothing. Speeds up kernel compilation by 1.375*10^-20001 seconds. But leave the most moxious comment in msdosfs_vfsops untouched.
|
1.52 |
| 29-Oct-2008 |
reinoud | branches: 1.52.2; Fix to prevent a closed sequential media to be opened for read/write.
|
1.51 |
| 27-Sep-2008 |
reinoud | branches: 1.51.2; Switch UDF over to the vfs_dirhash.c dirhash code.
|
1.50 |
| 29-Aug-2008 |
reinoud | Remove all remaining traces of UDF_READWRITE since it has been removed as option.
|
1.49 |
| 29-Aug-2008 |
reinoud | forgot to destroy an additional mutex and an condition variable.
|
1.48 |
| 08-Aug-2008 |
reinoud | Remove the need for the kernel option UDF_READWRITE to be able to write to discs since writing is mature enough.
|
1.47 |
| 06-Aug-2008 |
reinoud | Rewrite allocation scheme's determination and implementation replacing the old somewhat naive selection scheme that didn't allow different allocation settings for nodes, directory information (FIDs) and data.
Also fix some curious side-effects of atime updates on RMW devices.
|
1.46 |
| 28-Jul-2008 |
reinoud | Streamline allocation to prepare it for metadata partition. Also add preliminary Metadata partition write support but its disabled still since its not finished yet and not functioning correctly. All other formats are checked and should work fine.
|
1.45 |
| 27-Jul-2008 |
reinoud | Unify naming scheme and source code beautify for better readablility.
|
1.44 |
| 26-Jul-2008 |
reinoud | Forgot to rename those two references to write_space_bitmap too.
|
1.43 |
| 22-Jul-2008 |
reinoud | Limit the UDF dirhash to a configurable amount of memory. The performance penalty even with a limited dirhash of 128kb is acceptable but it should be set by machine memory size though.
|
1.42 |
| 19-Jul-2008 |
reinoud | Limit sectorsize to max. 4096 bytes. This prevents a panic when declaring the node pool since standard pools are limited upto 4096 aparently. Pagesize limit even?
|
1.41 |
| 18-Jul-2008 |
reinoud | Instead of bombing out when trying to mount a disc RW when UDF_READWRITE is not defined, downgrade it to a read-only mount.
|
1.40 |
| 17-Jul-2008 |
reinoud | Implement directory hashing to speed up directory traversals. Speed improvements of at least 4 times in untarring and roughly 100 to 500 times on file creation in big directories. Lookup of files was O(n*n) and is now O(1) even for file creation. Free spaces in the directory are kept in a seperate list for fast file creation.
The postmark benchmark gives:
UDF old: pm>set transactions 2000 pm>set number 3000 pm>run Creating files...Done Performing transactions..........Done Deleting files...Done Time: 1593 seconds total 681 seconds of transactions (2 per second)
Files: 3956 created (2 per second) Creation alone: 3000 files (4 per second) Mixed with transactions: 956 files (1 per second) 990 read (1 per second) 1010 appended (1 per second) 3956 deleted (2 per second) Deletion alone: 2912 files (9 per second) Mixed with transactions: 1044 files (1 per second)
Data: 5.26 megabytes read (3.38 kilobytes per second) 21.93 megabytes written (14.10 kilobytes per second) pm>
UDF new: pm>set transactions 2000 pm>set number 3000 pm>run Creating files...Done Performing transactions..........Done Deleting files...Done Time: 19 seconds total 3 seconds of transactions (666 per second)
Files: 3956 created (208 per second) Creation alone: 3000 files (230 per second) Mixed with transactions: 956 files (318 per second) 990 read (330 per second) 1010 appended (336 per second) 3956 deleted (208 per second) Deletion alone: 2912 files (970 per second) Mixed with transactions: 1044 files (348 per second)
Data: 5.26 megabytes read (283.66 kilobytes per second) 21.93 megabytes written (1.15 megabytes per second)
|
1.39 |
| 28-Jun-2008 |
rumble | branches: 1.39.2; Create sysctl entries during module initialisation and destroy them appropriately.
Many of these file systems are now ready for modularisation.
|
1.38 |
| 14-May-2008 |
reinoud | branches: 1.38.2; Import writing part of the UDF file system making optical media like CD's and DVD's behave like floppy discs. Writing is supported upto and including version 2.01; version 2.50 and 2.60 will follow.
Also extending the UDF implementation to support symbolic links and hardlinks.
Added are the mmcformat(8) tool to format rewritable CD/DVD discs and newfs_udf(8).
Limitations: all operations can be performed on the file system though the sheduling is currently optimised for archiving workloads.
mv(1)/rename(2) is currently only implemented for non-directories.
|
1.37 |
| 10-May-2008 |
rumble | Convert file systems to dynamically attach with the new module interface. Make VFS hooks dynamic while we're here and say farewell to VFS_ATTACH and VFS_HOOKS_ATTACH linksets.
As a consequence, most of the file systems can now be loaded as new style modules.
Quick sanity check by ad@.
|
1.36 |
| 29-Apr-2008 |
ad | branches: 1.36.2; PR kern/38057 ffs makes assuptions about devvp file system PR kern/33406 softdeps get stuck in endless loop
Introduce VFS_FSYNC() and call it when syncing a block device, if it has a mounted file system.
|
1.35 |
| 28-Jan-2008 |
dholland | branches: 1.35.6; 1.35.8; 1.35.10; Fix some race conditions in rename. Introduce a per-FS rename lock and new vfsops to manipulate it. Get this lock while renaming. Also add another relookup() in do_sys_rename, which is a hack to kludge around some of the worst deficiencies of ufs_rename. reviewed-by: pooka (and an earlier rev by ad) posted on tech-kern with no objections.
|
1.34 |
| 24-Jan-2008 |
ad | specfs changes for PR kern/37717 (raidclose() is no longer called on shutdown). There are still problems with device access and a PR will be filed.
- Kill checkalias(). Allow multiple vnodes to reference a single device.
- Don't play dangerous tricks with block vnodes to ensure that only one vnode can describe a block device. Instead, prohibit concurrent opens of block devices. As a bonus remove the unreliable code that prevents multiple file system mounts on the same device. It's no longer needed.
- Track opens by vnode and by device. Issue cdev_close() when the last open goes away, instead of abusing vnode::v_usecount to tell if the device is open.
|
1.33 |
| 11-Dec-2007 |
lukem | use __KERNEL_RCSID() instead of __RCSID()
|
1.32 |
| 08-Dec-2007 |
pooka | branches: 1.32.2; 1.32.4; Remove cn_lwp from struct componentname. curlwp should be used from on. The NDINIT() macro no longer takes the lwp parameter and associates the credentials of the calling thread with the namei structure.
|
1.31 |
| 26-Nov-2007 |
pooka | branches: 1.31.2; Remove the "struct lwp *" argument from all VFS and VOP interfaces. The general trend is to remove it from all kernel interfaces and this is a start. In case the calling lwp is desired, curlwp should be used.
quick consensus on tech-kern
|
1.30 |
| 10-Oct-2007 |
ad | branches: 1.30.4; Merge from vmlocking:
- Split vnode::v_flag into three fields, depending on field locking. - simple_lock -> kmutex in a few places. - Fix some simple locking problems.
|
1.29 |
| 31-Jul-2007 |
pooka | branches: 1.29.2; 1.29.4; 1.29.6; 1.29.8; * nuke the nameidata parameter from VFS_MOUNT(). Nobody on tech-kern knew what it was supposed to be used for and wrstuden gave a go-ahead * while rototilling, convert file systems which went easily to use VFS_PROTOS() instead of manually prototyping the methods
|
1.28 |
| 26-Jul-2007 |
pooka | Use eopnotsupp() instead of vfs_stdsuspendctl() and retire the latter.
|
1.27 |
| 17-Jul-2007 |
pooka | branches: 1.27.2; Make set_statvfs_info() take a parameter for the vfs name instead of always retrieving it from mp->mnt_op->vfs_name
christos ok
|
1.26 |
| 12-Jul-2007 |
dsl | Change the VFS_MOUNT() interface so that the 'data' buffer passed to the fs code is a kernel buffer, pass though the length of the buffer as well. Since the length of the userspace buffer isn'it (yet) passed through the mount system call, add a field to the vfsops structure containing the default length. Split sys_mount() for calls from compat code. Ride one of the recent kernel version changes - old fs LKMs will load, but sys_mount() will reject any attempt to use them.
|
1.25 |
| 30-Jun-2007 |
pooka | Using POOL_INIT here makes no sense, since file systems always have an init method. So get rid of it and #ifdef _LKM and just always init in the init method. Give malloc types the same treatment. Makes file systems nicer to work with in linksetless environments and fixes a few LKM discrepancies.
|
1.24 |
| 29-Apr-2007 |
msaitoh | fix typos
|
1.23 |
| 12-Mar-2007 |
ad | branches: 1.23.2; Pass an ipl argument to pool_init/POOL_INIT to be used when initializing the pool's lock.
|
1.22 |
| 29-Jan-2007 |
hubertf | branches: 1.22.2; 1.22.6; Remove more duplicate headers. Patch by Slava Semushin <slava.semushin@gmail.com>
Again, this was tested by comparing obj files from a pristine and a patched source tree against an i386/ALL kernel, and also for src/sbin/fsck_ffs, src/sbin/fsdb and src/usr.sbin/makefs. Only changes in assert() line numbers were detected in 'objdump -d' output.
|
1.21 |
| 19-Jan-2007 |
hannken | New file system suspension API to replace vn_start_write and vn_finished_write. The suspension helpers are now put into file system specific operations. This means every file system not supporting these helpers cannot be suspended and therefore snapshots are no longer possible.
Implemented for file systems of type ffs.
The new API is enabled on a kernel option NEWVNGATE. This option is not enabled by default in any kernel config.
Presented and discussed on tech-kern with much input from Bill Studenmund <wrstuden@netbsd.org> and YAMAMOTO Takashi <yamt@netbsd.org>.
Welcome to 4.99.9 (new vfs op vfs_suspendctl).
|
1.20 |
| 04-Jan-2007 |
elad | Consistent usage of KAUTH_GENERIC_ISSUSER.
|
1.19 |
| 04-Jan-2007 |
reinoud | Implement read-only access to UDF 2.50 and UDF 2.60 discs that use metadata partition mappings. This brings the NetBSD implementation to read all discs upto date and will read all discs currently defined by OSTA.
|
1.18 |
| 16-Nov-2006 |
christos | branches: 1.18.2; __unused removal on arguments; approved by core.
|
1.17 |
| 20-Oct-2006 |
reinoud | Replace the LIST structure mp->mnt_vnodelist to a TAILQ structure since all vnodes were synced and processed backwards. This meant that the last accessed node was processed first and the earlierst last.
An extra benefit is the removal of the ugly hack from the Berkly days on LFS.
In the proces, i've also replaced the various variations hand written loops by the TAILQ_FOREACH() macro's.
|
1.16 |
| 12-Oct-2006 |
christos | - sprinkle __unused on function decls. - fix a couple of unused bugs - no more -Wno-unused for i386
|
1.15 |
| 03-Oct-2006 |
reinoud | Fix memory leaks on mounting and dismounting UDF volumes.
|
1.14 |
| 29-Sep-2006 |
reinoud | Add `vfs.udf.verbose' sysctl when running a DEBUG kernel to dynamically set the udf_verbose variable. So when something goes wrong, it can be examined on the spot without needing to reboot a new kernel and possibly loosing state.
|
1.13 |
| 05-Sep-2006 |
reinoud | branches: 1.13.2; 1.13.4; 1.13.6; Fix locking scheme in udf_mount() to follow more the other filingsystems.
For yet unknown reasons passing the LOCKLEAF flag to namei() did return a locked vnode as was meant but would panic when a raw device was passed.
|
1.12 |
| 03-Sep-2006 |
christos | add missing initializers
|
1.11 |
| 22-Aug-2006 |
reinoud | Fix pool allocation/freeing problem for once and for all correctly. Since it was initialised quite late due to its reliance on disc data the mount process could have stopped before initialising and thus could panic again only now for uninitialising an not initialised pool! *sigh*
|
1.10 |
| 21-Aug-2006 |
reinoud | Fix spurious panic when twice remounting a bad filingsystem. It then gets the same memory block allocated as before and it bombs out on its descriptor pool allready being initialised. It turns out that the pool was not allways destroyed. This fix ought to clean it up whatever the cause of the mishap that results in a reject.
|
1.9 |
| 10-Aug-2006 |
reinoud | Fix panic on badly or curruptly formatted discs due to an oddity in the error handling chain.
If NetBSD 4.0 is allready branched at this time this ought to be pulled up.
|
1.8 |
| 23-Jul-2006 |
ad | branches: 1.8.2; Use the LWP cached credentials where sane.
|
1.7 |
| 13-Jul-2006 |
martin | Fix alignement problems for fhandle_t, exposed by gcc4.1.
While touching all vptofh/fhtovp functions, get rid of VFS_MAXFIDSIZ, version the getfh(2) syscall and explicitly pass the size available in the filehandle from userland.
Discussed on tech-kern, with lots of help from yamt (thanks!).
|
1.6 |
| 12-Jun-2006 |
christos | branches: 1.6.2; 1.6.4; remove ; from };
|
1.5 |
| 15-May-2006 |
christos | branches: 1.5.2; kauth fallout
|
1.4 |
| 14-May-2006 |
elad | integrate kauth.
|
1.3 |
| 25-Apr-2006 |
snj | s/allready/already/
|
1.2 |
| 02-Feb-2006 |
reinoud | branches: 1.2.2; 1.2.4; 1.2.6; 1.2.8; 1.2.10; Fix $NetBSD$ tags. (sorry)
|
1.1 |
| 02-Feb-2006 |
reinoud | Initial import of a UDF file system implementation for NetBSD.
The code supports read access to all media types that CD/DVD type drives can recognize including DVD-RAM and BD- drives as well as harddisc partions and vnd devices. UDF versions upto the latest 2.60 are to be supported though due to lack of test media version 2.50 and 2.60 are not implemented yet though easy to add. Both open and closed media are supported.
Write access is planned and in preparation. To facilitate this some hooks are present in the code that are not strictly needed in a read-only implementation but which allow writing to be added more easily.
Implemented and tested media types are CD-ROM, CD-R, CD-RW, CD-MRW, DVD-ROM, DVD*R, DVD*RW, DVD+MRW but the same code can also read DVD-RAM, HD-DVD and BluRay discs. Also vnd devices have been tested with several sector sizes.
Discs created and written by UDFclient, Nero's InCD and Roxio's DirectCD/Drag2Disc read fine.
|
1.2.10.1 |
| 24-May-2006 |
tron | Merge 2006-05-24 NetBSD-current into the "peter-altq" branch.
|
1.2.8.2 |
| 11-May-2006 |
elad | sync with head
|
1.2.8.1 |
| 08-Mar-2006 |
elad | Adapt to kernel authorization KPI.
|
1.2.6.5 |
| 14-Sep-2006 |
yamt | sync with head.
|
1.2.6.4 |
| 03-Sep-2006 |
yamt | sync with head.
|
1.2.6.3 |
| 11-Aug-2006 |
yamt | sync with head
|
1.2.6.2 |
| 26-Jun-2006 |
yamt | sync with head.
|
1.2.6.1 |
| 24-May-2006 |
yamt | sync with head.
|
1.2.4.2 |
| 18-Feb-2006 |
yamt | sync with head.
|
1.2.4.1 |
| 02-Feb-2006 |
yamt | file udf_vfsops.c was added on branch yamt-uio_vmspace on 2006-02-18 15:39:18 +0000
|
1.2.2.1 |
| 01-Jun-2006 |
kardel | Sync with head.
|
1.5.2.1 |
| 19-Jun-2006 |
chap | Sync with head.
|
1.6.4.9 |
| 04-Feb-2008 |
yamt | sync with head.
|
1.6.4.8 |
| 21-Jan-2008 |
yamt | sync with head
|
1.6.4.7 |
| 07-Dec-2007 |
yamt | sync with head
|
1.6.4.6 |
| 27-Oct-2007 |
yamt | sync with head.
|
1.6.4.5 |
| 03-Sep-2007 |
yamt | sync with head.
|
1.6.4.4 |
| 26-Feb-2007 |
yamt | sync with head.
|
1.6.4.3 |
| 30-Dec-2006 |
yamt | sync with head.
|
1.6.4.2 |
| 21-Jun-2006 |
yamt | sync with head.
|
1.6.4.1 |
| 12-Jun-2006 |
yamt | file udf_vfsops.c was added on branch yamt-lazymbuf on 2006-06-21 15:09:37 +0000
|
1.6.2.1 |
| 13-Jul-2006 |
gdamore | Merge from HEAD.
|
1.8.2.4 |
| 08-Sep-2006 |
rpaulo | Pull up following revision(s) (requested by reinoud in ticket #125): sys/fs/udf/udf_subr.c: revision 1.15 sys/fs/udf/udf_vfsops.c: revision 1.13 sys/fs/udf/ecma167-udf.h: revision 1.4 Add shortcut for struct long_ad 's Unique ID hint that covers the lower 32 bits of the targeted files 64 bits Unique ID for recovery purposes. Fix locking scheme in udf_mount() to follow more the other filingsystems. For yet unknown reasons passing the LOCKLEAF flag to namei() did return a locked vnode as was meant but would panic when a raw device was passed. Fix copying too much space from a small buffer. The chances of it actually happening are small but corrupt media could trigger it.
|
1.8.2.3 |
| 27-Aug-2006 |
riz | Pull up following revision(s) (requested by reinoud in ticket #50): sys/fs/udf/udf_subr.c: revision 1.14 sys/fs/udf/udf.h: revision 1.6 sys/fs/udf/udf_vfsops.c: revision 1.11 Fix pool allocation/freeing problem for once and for all correctly. Since it was initialised quite late due to its reliance on disc data the mount process could have stopped before initialising and thus could panic again only now for uninitialising an not initialised pool! *sigh*
|
1.8.2.2 |
| 23-Aug-2006 |
tron | Pull up following revision(s) (requested by reinoud in ticket #45): sys/fs/udf/udf_vfsops.c: revision 1.10 Fix spurious panic when twice remounting a bad filingsystem. It then gets the same memory block allocated as before and it bombs out on its descriptor pool allready being initialised. It turns out that the pool was not allways destroyed. This fix ought to clean it up whatever the cause of the mishap that results in a reject.
|
1.8.2.1 |
| 12-Aug-2006 |
riz | Pull up following revision(s) (requested by reinoud in ticket #12): sys/fs/udf/udf_vfsops.c: revision 1.9 sys/dev/scsipi/cd.c: revision 1.243 Fix panic on badly or curruptly formatted discs due to an oddity in the error handling chain. If NetBSD 4.0 is allready branched at this time this ought to be pulled up. Fix incorrect `last possible lba' reporting, remove some empty lines and add mmc classification for some still rare HD DVD device types.
|
1.13.6.2 |
| 10-Dec-2006 |
yamt | sync with head.
|
1.13.6.1 |
| 22-Oct-2006 |
yamt | sync with head
|
1.13.4.2 |
| 09-Sep-2006 |
rpaulo | sync with head
|
1.13.4.1 |
| 05-Sep-2006 |
rpaulo | file udf_vfsops.c was added on branch rpaulo-netinet-merge-pcb on 2006-09-09 02:57:06 +0000
|
1.13.2.3 |
| 01-Feb-2007 |
ad | Sync with head.
|
1.13.2.2 |
| 12-Jan-2007 |
ad | Sync with head.
|
1.13.2.1 |
| 18-Nov-2006 |
ad | Sync with head.
|
1.18.2.1 |
| 04-Jan-2007 |
bouyer | Pull up following revision(s) (requested by reinoud in ticket #332): sys/fs/udf/udf_subr.c: revision 1.26 sys/fs/udf/udf.h: revision 1.9 sys/fs/udf/udf_vfsops.c: revision 1.19 Implement read-only access to UDF 2.50 and UDF 2.60 discs that use metadata partition mappings. This brings the NetBSD implementation to read all discs upto date and will read all discs currently defined by OSTA.
|
1.22.6.7 |
| 20-Aug-2007 |
ad | Sync with HEAD.
|
1.22.6.6 |
| 15-Jul-2007 |
ad | Sync with head.
|
1.22.6.5 |
| 17-Jun-2007 |
ad | - Increase the number of thread priorities from 128 to 256. How the space is set up is to be revisited. - Implement soft interrupts as kernel threads. A generic implementation is provided, with hooks for fast-path MD code that can run the interrupt threads over the top of other threads executing in the kernel. - Split vnode::v_flag into three fields, depending on how the flag is locked (by the interlock, by the vnode lock, by the file system). - Miscellaneous locking fixes and improvements.
|
1.22.6.4 |
| 09-Jun-2007 |
ad | Sync with head.
|
1.22.6.3 |
| 08-Jun-2007 |
ad | Sync with head.
|
1.22.6.2 |
| 05-Apr-2007 |
ad | Compile fixes.
|
1.22.6.1 |
| 13-Mar-2007 |
ad | Sync with head.
|
1.22.2.2 |
| 07-May-2007 |
yamt | sync with head.
|
1.22.2.1 |
| 24-Mar-2007 |
yamt | sync with head.
|
1.23.2.1 |
| 11-Jul-2007 |
mjf | Sync with head.
|
1.27.2.1 |
| 15-Aug-2007 |
skrll | Sync with HEAD.
|
1.29.8.2 |
| 31-Jul-2007 |
pooka | * nuke the nameidata parameter from VFS_MOUNT(). Nobody on tech-kern knew what it was supposed to be used for and wrstuden gave a go-ahead * while rototilling, convert file systems which went easily to use VFS_PROTOS() instead of manually prototyping the methods
|
1.29.8.1 |
| 31-Jul-2007 |
pooka | file udf_vfsops.c was added on branch matt-mips64 on 2007-07-31 21:14:20 +0000
|
1.29.6.1 |
| 14-Oct-2007 |
yamt | sync with head.
|
1.29.4.3 |
| 23-Mar-2008 |
matt | sync with HEAD
|
1.29.4.2 |
| 09-Jan-2008 |
matt | sync with HEAD
|
1.29.4.1 |
| 06-Nov-2007 |
matt | sync with HEAD
|
1.29.2.3 |
| 09-Dec-2007 |
jmcneill | Sync with HEAD.
|
1.29.2.2 |
| 27-Nov-2007 |
joerg | Sync with HEAD. amd64 Xen support needs testing.
|
1.29.2.1 |
| 26-Oct-2007 |
joerg | Sync with HEAD.
Follow the merge of pmap.c on i386 and amd64 and move pmap_init_tmp_pgtbl into arch/x86/x86/pmap.c. Modify the ACPI wakeup code to restore CR4 before jumping back into kernel space as the large page option might cover that.
|
1.30.4.3 |
| 18-Feb-2008 |
mjf | Sync with HEAD.
|
1.30.4.2 |
| 27-Dec-2007 |
mjf | Sync with HEAD.
|
1.30.4.1 |
| 08-Dec-2007 |
mjf | Sync with HEAD.
|
1.31.2.1 |
| 26-Dec-2007 |
ad | Sync with head.
|
1.32.4.1 |
| 13-Dec-2007 |
bouyer | Sync with HEAD
|
1.32.2.1 |
| 11-Dec-2007 |
yamt | sync with head.
|
1.35.10.4 |
| 11-Aug-2010 |
yamt | sync with head.
|
1.35.10.3 |
| 18-Jul-2009 |
yamt | sync with head.
|
1.35.10.2 |
| 04-May-2009 |
yamt | sync with head.
|
1.35.10.1 |
| 16-May-2008 |
yamt | sync with head.
|
1.35.8.1 |
| 18-May-2008 |
yamt | sync with head.
|
1.35.6.5 |
| 17-Jan-2009 |
mjf | Sync with HEAD.
|
1.35.6.4 |
| 05-Oct-2008 |
mjf | Sync with HEAD.
|
1.35.6.3 |
| 28-Sep-2008 |
mjf | Sync with HEAD.
|
1.35.6.2 |
| 29-Jun-2008 |
mjf | Sync with HEAD.
|
1.35.6.1 |
| 02-Jun-2008 |
mjf | Sync with HEAD.
|
1.36.2.3 |
| 10-Oct-2008 |
skrll | Sync with HEAD.
|
1.36.2.2 |
| 18-Sep-2008 |
wrstuden | Sync with wrstuden-revivesa-base-2.
|
1.36.2.1 |
| 23-Jun-2008 |
wrstuden | Sync w/ -current. 34 merge conflicts to follow.
|
1.38.2.5 |
| 31-Jul-2008 |
simonb | Sync with head.
|
1.38.2.4 |
| 28-Jul-2008 |
simonb | Sync with head.
|
1.38.2.3 |
| 22-Jul-2008 |
simonb | Sync with head.
|
1.38.2.2 |
| 18-Jul-2008 |
simonb | Sync with head.
|
1.38.2.1 |
| 03-Jul-2008 |
simonb | Sync with head.
|
1.39.2.2 |
| 13-Dec-2008 |
haad | Update haad-dm branch to haad-dm-base2.
|
1.39.2.1 |
| 19-Oct-2008 |
haad | Sync with HEAD.
|
1.51.2.3 |
| 28-Apr-2009 |
skrll | Sync with HEAD.
|
1.51.2.2 |
| 03-Mar-2009 |
skrll | Sync with HEAD.
|
1.51.2.1 |
| 19-Jan-2009 |
skrll | Sync with HEAD.
|
1.52.2.4 |
| 25-Apr-2014 |
sborrill | Pull up the following revisions(s) (requested by maxv in ticket #1901): sys/kern/vfs_syscalls.c: revision 1.478, 1.480 via patch sys/coda/coda_vfsops.c: revision 1.81 sys/fs/adosfs/advfsops.c: revision 1.70 sys/fs/cd9660/cd9660_vfsops.c: revision 1.84 sys/fs/efs/efs_vfsops.c: revision 1.25 sys/fs/filecorefs/filecore_vfsops.c: revision 1.76 sys/fs/hfs/hfs_vfsops.c: revision 1.31 sys/fs/msdosfs/msdosfs_vfsops.c: revision 1.107 sys/fs/ntfs/ntfs_vfsops.c: revision 1.94 sys/fs/ptyfs/ptyfs_vfsops.c: revision 1.50 via patch sys/fs/puffs/puffs_vfsops.c: revision 1.110 via patch sys/fs/smbfs/smbfs_vfsops.c: revision 1.100 sys/fs/sysvbfs/sysvbfs_vfsops.c: revision 1.43 sys/fs/tmpfs/tmpfs_vfsops.c: revision 1.59 via patch sys/fs/udf/udf_vfsops.c: revision 1.67 sys/fs/union/union_vfsops.c: revision 1.72 sys/fs/unionfs/unionfs_vfsops.c: revision 1.13 sys/kern/vfs_syscalls.c: revision 1.479 sys/miscfs/nullfs/null_vfsops.c: revision 1.88 via patch sys/miscfs/overlay/overlay_vfsops.c: revision 1.61 sys/miscfs/procfs/procfs_vfsops.c: revision 1.91 sys/miscfs/umapfs/umap_vfsops.c: revision 1.92 sys/nfs/nfs_vfsops.c: revision 1.227 sys/ufs/ext2fs/ext2fs_vfsops.c: revision 1.180 sys/ufs/ffs/ffs_vfsops.c: revision 1.297 sys/ufs/lfs/lfs_vfsops.c: revision 1.321 sys/ufs/mfs/mfs_vfsops.c: revision 1.107
Due to missing checks in the mount syscall, and a wrong assumption on the file systems side, the kernel could allocate an unbounded or zero-sized memory buffer, and could dereference a NULL pointer when particular arguments are given by a user.
|
1.52.2.3 |
| 09-Jul-2009 |
snj | branches: 1.52.2.3.2; 1.52.2.3.6; Apply patch (requested by reinoud in ticket #852): Numerous UDF improvements: - a much saner rmw backend - free space management done right - the high system time usage when encountering huge numbers of nodes are a thing of the past due to refactoring - various small fixes
|
1.52.2.2 |
| 18-Feb-2009 |
snj | branches: 1.52.2.2.4; Pull up following revision(s) (requested by reinoud in ticket #446): sys/fs/udf/udf_vfsops.c: revision 1.55 If mounting for read-write dont allow a session number to be specified since its currently still misbehaving. If supported later, it would allow one or a series of sessions on a sequential recordable media to be ignored as if they never were created. Also fix a small comment: its not the direct but the bootstrap disc strategy that we close down.
|
1.52.2.1 |
| 18-Dec-2008 |
snj | Pull up following revision(s) (requested by reinoud in ticket #192): sys/fs/udf/udf_subr.c: revision 1.79 sys/fs/udf/udf_vfsops.c: revision 1.54 Check for a node being root on node creation so when the root node is disposed of when working deep into the directory tree it can reliably be reget and marked correctly as the FS root. Fixed pwd(1) lock panic and possible endless loop in other tools.
|
1.52.2.3.6.1 |
| 28-Apr-2014 |
sborrill | Pull up the following revisions(s) (requested by maxv in ticket #1901): sys/kern/vfs_syscalls.c: revision 1.478, 1.480 via patch sys/coda/coda_vfsops.c: revision 1.81 sys/fs/adosfs/advfsops.c: revision 1.70 sys/fs/cd9660/cd9660_vfsops.c: revision 1.84 sys/fs/efs/efs_vfsops.c: revision 1.25 sys/fs/filecorefs/filecore_vfsops.c: revision 1.76 sys/fs/hfs/hfs_vfsops.c: revision 1.31 sys/fs/msdosfs/msdosfs_vfsops.c: revision 1.107 sys/fs/ntfs/ntfs_vfsops.c: revision 1.94 sys/fs/ptyfs/ptyfs_vfsops.c: revision 1.50 via patch sys/fs/puffs/puffs_vfsops.c: revision 1.110 via patch sys/fs/smbfs/smbfs_vfsops.c: revision 1.100 sys/fs/sysvbfs/sysvbfs_vfsops.c: revision 1.43 sys/fs/tmpfs/tmpfs_vfsops.c: revision 1.59 via patch sys/fs/udf/udf_vfsops.c: revision 1.67 sys/fs/union/union_vfsops.c: revision 1.72 sys/fs/unionfs/unionfs_vfsops.c: revision 1.13 sys/kern/vfs_syscalls.c: revision 1.479 sys/miscfs/nullfs/null_vfsops.c: revision 1.88 via patch sys/miscfs/overlay/overlay_vfsops.c: revision 1.61 sys/miscfs/procfs/procfs_vfsops.c: revision 1.91 sys/miscfs/umapfs/umap_vfsops.c: revision 1.92 sys/nfs/nfs_vfsops.c: revision 1.227 sys/ufs/ext2fs/ext2fs_vfsops.c: revision 1.180 sys/ufs/ffs/ffs_vfsops.c: revision 1.297 sys/ufs/lfs/lfs_vfsops.c: revision 1.321 sys/ufs/mfs/mfs_vfsops.c: revision 1.107
Due to missing checks in the mount syscall, and a wrong assumption on the file systems side, the kernel could allocate an unbounded or zero-sized memory buffer, and could dereference a NULL pointer when particular arguments are given by a user.
|
1.52.2.3.2.1 |
| 28-Apr-2014 |
sborrill | Pull up the following revisions(s) (requested by maxv in ticket #1901): sys/kern/vfs_syscalls.c: revision 1.478, 1.480 via patch sys/coda/coda_vfsops.c: revision 1.81 sys/fs/adosfs/advfsops.c: revision 1.70 sys/fs/cd9660/cd9660_vfsops.c: revision 1.84 sys/fs/efs/efs_vfsops.c: revision 1.25 sys/fs/filecorefs/filecore_vfsops.c: revision 1.76 sys/fs/hfs/hfs_vfsops.c: revision 1.31 sys/fs/msdosfs/msdosfs_vfsops.c: revision 1.107 sys/fs/ntfs/ntfs_vfsops.c: revision 1.94 sys/fs/ptyfs/ptyfs_vfsops.c: revision 1.50 via patch sys/fs/puffs/puffs_vfsops.c: revision 1.110 via patch sys/fs/smbfs/smbfs_vfsops.c: revision 1.100 sys/fs/sysvbfs/sysvbfs_vfsops.c: revision 1.43 sys/fs/tmpfs/tmpfs_vfsops.c: revision 1.59 via patch sys/fs/udf/udf_vfsops.c: revision 1.67 sys/fs/union/union_vfsops.c: revision 1.72 sys/fs/unionfs/unionfs_vfsops.c: revision 1.13 sys/kern/vfs_syscalls.c: revision 1.479 sys/miscfs/nullfs/null_vfsops.c: revision 1.88 via patch sys/miscfs/overlay/overlay_vfsops.c: revision 1.61 sys/miscfs/procfs/procfs_vfsops.c: revision 1.91 sys/miscfs/umapfs/umap_vfsops.c: revision 1.92 sys/nfs/nfs_vfsops.c: revision 1.227 sys/ufs/ext2fs/ext2fs_vfsops.c: revision 1.180 sys/ufs/ffs/ffs_vfsops.c: revision 1.297 sys/ufs/lfs/lfs_vfsops.c: revision 1.321 sys/ufs/mfs/mfs_vfsops.c: revision 1.107
Due to missing checks in the mount syscall, and a wrong assumption on the file systems side, the kernel could allocate an unbounded or zero-sized memory buffer, and could dereference a NULL pointer when particular arguments are given by a user.
|
1.52.2.2.4.1 |
| 21-Apr-2010 |
matt | sync to netbsd-5
|
1.55.2.2 |
| 23-Jul-2009 |
jym | Sync with HEAD.
|
1.55.2.1 |
| 13-May-2009 |
jym | Sync with HEAD.
Commit is split, to avoid a "too many arguments" protocol error.
|
1.59.4.1 |
| 03-Jul-2010 |
rmind | sync with head
|
1.59.2.1 |
| 17-Aug-2010 |
uebayasi | Sync with HEAD.
|
1.61.2.2 |
| 22-May-2014 |
yamt | sync with head.
for a reference, the tree before this commit was tagged as yamt-pagecache-tag8.
this commit was splitted into small chunks to avoid a limitation of cvs. ("Protocol error: too many arguments")
|
1.61.2.1 |
| 17-Apr-2012 |
yamt | sync with head
|
1.62.12.1 |
| 21-Apr-2014 |
bouyer | 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).
|
1.62.10.1 |
| 21-Apr-2014 |
bouyer | 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).
|
1.62.6.1 |
| 21-Apr-2014 |
bouyer | 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).
|
1.62.4.1 |
| 05-Apr-2012 |
mrg | sync to latest -current.
|
1.63.4.1 |
| 18-May-2014 |
rmind | sync with head
|
1.63.2.2 |
| 03-Dec-2017 |
jdolecek | update from HEAD
|
1.63.2.1 |
| 20-Aug-2014 |
tls | Rebase to HEAD as of a few days ago.
|
1.66.2.1 |
| 10-Aug-2014 |
tls | Rebase.
|
1.67.4.4 |
| 28-Aug-2017 |
skrll | Sync with HEAD
|
1.67.4.3 |
| 19-Mar-2016 |
skrll | Sync with HEAD
|
1.67.4.2 |
| 22-Sep-2015 |
skrll | Sync with HEAD
|
1.67.4.1 |
| 06-Apr-2015 |
skrll | Sync with HEAD
|
1.73.4.1 |
| 21-Apr-2017 |
bouyer | Sync with HEAD
|
1.73.2.3 |
| 26-Apr-2017 |
pgoyette | Sync with HEAD
|
1.73.2.2 |
| 20-Mar-2017 |
pgoyette | Sync with HEAD
|
1.73.2.1 |
| 20-Jul-2016 |
pgoyette | Adapt machine-independant code to the new {b,c}devsw reference-counting (using localcount(9)). All callers of {b,c}devsw_lookup() now call {b,c}devsw_lookup_acquire() which retains a reference on the 'struct {b,c}devsw'. This reference must be released by the caller once it is finished with the structure's content (or other data that would disappear if the 'struct {b,c}devsw' were to disappear).
|
1.75.6.1 |
| 01-Jul-2017 |
snj | Pull up following revision(s) (requested by hannken in ticket #75): sys/fs/udf/udf_vfsops.c: revision 1.76 No need to call vflush from failing udf_mount(). If the system nodes really have to disappear we should change vrele() to vrecycle() here.
|
1.75.4.1 |
| 27-Apr-2017 |
pgoyette | Restore all work from the former pgoyette-localcount branch (which is now abandoned doe to cvs merge botch).
The branch now builds, and installs via anita. There are still some problems (cgd is non-functional and all atf tests time-out) but they will get resolved soon.
|
1.76.12.1 |
| 17-Jan-2020 |
ad | Sync with head.
|
1.76.10.1 |
| 13-Mar-2022 |
martin | Pull up following revision(s), all via patch, requested by reinoud in ticket #1432:
sys/fs/udf/udf_vfsops.c: revision 1.83 sys/fs/udf/udf_allocation.c: revision 1.45 sys/fs/udf/udf_subr.c: revision 1.160 sys/fs/udf/udf_subr.c: revision 1.161
While searching the VAT on recordable media, search the last sector too! This fixes Win10 formatted discs from being mounted incorrectly.
Make sysctl udf.verbose dependent on UDF_DEBUG instead of DEBUG
Fix serious issue with recordable media formatted with Win10. When closing it after modification the VAT was written out corrupted making the disc unreadable anymore on remount. Thanks for ig@ for spotting it in the wild!
On freeing a virtual address in the VAT, use the correct value; this might confuse other implementations who can reject the VAT on this.
|
1.76.6.2 |
| 21-Apr-2020 |
martin | Sync with HEAD
|
1.76.6.1 |
| 08-Apr-2020 |
martin | Merge changes from current as of 20200406
|
1.78.2.1 |
| 20-Apr-2020 |
bouyer | Sync with HEAD
|
1.80.6.1 |
| 01-Aug-2021 |
thorpej | Sync with HEAD.
|