src-test2/sys/fs, branch release/5.2.0 FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F5.2.0 2003-12-17T11:35:11Z MFC: Make msdosfs long filenames matching case insensitive again. 2003-12-17T11:35:11Z Tim J. Robbins tjr@FreeBSD.org 2003-12-17T11:35:11Z urn:sha1:48455098b087fd6867632a5c5f751ad92e571165 Approved by: re (scottl) MFC rev. 1.33: Don't sign-extend characters in file names. 2003-12-17T09:35:44Z Tim J. Robbins tjr@FreeBSD.org 2003-12-17T09:35:44Z urn:sha1:befc6801c45e35e53d61e4f3f1b4397d2f6c3ff6 Approved by: re (scottl) This commit was manufactured by cvs2svn to create branch 'RELENG_5_2'. 2003-12-07T03:02:28Z cvs2svn cvs2svn@FreeBSD.org 2003-12-07T03:02:28Z urn:sha1:a348451bd8bd6d66bcb5b23f2aaec00e74c1292f Fix vnode locking in fdesc_setattr. Lock vnode before invoking 2003-11-19T04:14:42Z Alexander Kabaev kan@FreeBSD.org 2003-11-19T04:14:42Z urn:sha1:c39134984175e4daa676d6c8bfa92c6eb400ee9d VOP_SETATTR on it. Approved by: re@ (rwatson) Use "fip->fi_readers == 0 && fip->fi_writers == 0" as the condition for 2003-11-16T01:11:11Z Don Lewis truckman@FreeBSD.org 2003-11-16T01:11:11Z urn:sha1:95c6cd2f4b74c1636e51a7c7f528e4b98d5184ac disposing fifo resources in fifo_cleanup() instead using of "vp->v_usecount == 1". There may be other references to the vnode, for instance by nullfs, at the time fifo_open() or fifo_close() is called, which could cause a resource leak. Don't bother grabbing the vnode interlock in fifo_cleanup() since it no longer accesses v_usecount. - A sanity check in unionfs verifies that lookups of '.' return the 2003-11-14T08:23:13Z David Schultz das@FreeBSD.org 2003-11-14T08:23:13Z urn:sha1:95eac68fea1e2f1d90042618de228a21ce80039c vnode of the parent. However, this check should not be performed if the lookup failed. This change should fix "union_lookup returning . not same as startdir" panics people were seeing. The bug was introduced by an incomplete import of a NetBSD delta in rev 1.38. - Move the aforementioned check out from DIAGNOSTIC. Performance is the least of our unionfs worries. - Minor reorganization. PR: 53004 MFC after: 1 week Initialize b_iooffset correctly. 2003-11-13T09:58:09Z Poul-Henning Kamp phk@FreeBSD.org 2003-11-13T09:58:09Z urn:sha1:98d87dfecdb9b1024749ee43c6b0ebbf15c1287e Don't mess around with spare fields of public structures. 2003-11-12T09:54:07Z Poul-Henning Kamp phk@FreeBSD.org 2003-11-12T09:54:07Z urn:sha1:2178f0e34082e48f7517a47bcbc30defb7e4b820 Don't mess about with spare fields in public structures. 2003-11-12T09:52:10Z Poul-Henning Kamp phk@FreeBSD.org 2003-11-12T09:52:10Z urn:sha1:1054ba63be8ca5255db2ed4bcb0e58e1d9e324b7 Modify the MAC Framework so that instead of embedding a (struct label) 2003-11-12T03:14:31Z Robert Watson rwatson@FreeBSD.org 2003-11-12T03:14:31Z urn:sha1:eca8a663d442468f64e21ed869817b9048ab5a7b in various kernel objects to represent security data, we embed a (struct label *) pointer, which now references labels allocated using a UMA zone (mac_label.c). This allows the size and shape of struct label to be varied without changing the size and shape of these kernel objects, which become part of the frozen ABI with 5-STABLE. This opens the door for boot-time selection of the number of label slots, and hence changes to the bound on the number of simultaneous labeled policies at boot-time instead of compile-time. This also makes it easier to embed label references in new objects as required for locking/caching with fine-grained network stack locking, such as inpcb structures. This change also moves us further in the direction of hiding the structure of kernel objects from MAC policy modules, not to mention dramatically reducing the number of '&' symbols appearing in both the MAC Framework and MAC policy modules, and improving readability. While this results in minimal performance change with MAC enabled, it will observably shrink the size of a number of critical kernel data structures for the !MAC case, and should have a small (but measurable) performance benefit (i.e., struct vnode, struct socket) do to memory conservation and reduced cost of zeroing memory. NOTE: Users of MAC must recompile their kernel and all MAC modules as a result of this change. Because this is an API change, third party MAC modules will also need to be updated to make less use of the '&' symbol. Suggestions from: bmilekic Obtained from: TrustedBSD Project Sponsored by: DARPA, Network Associates Laboratories