<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/gnu/ext2fs/ext2_readwrite.c, branch releng/5.3</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=releng%2F5.3</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=releng%2F5.3'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2004-04-07T20:46:16Z</updated>
<entry>
<title>Remove advertising clause from University of California Regent's</title>
<updated>2004-04-07T20:46:16Z</updated>
<author>
<name>Warner Losh</name>
<email>imp@FreeBSD.org</email>
</author>
<published>2004-04-07T20:46:16Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=f36cfd49adb62472fd7009ecd4f0927c126ff785'/>
<id>urn:sha1:f36cfd49adb62472fd7009ecd4f0927c126ff785</id>
<content type='text'>
license, per letter dated July 22, 1999 and email from Peter Wemm,
Alan Cox and Robert Watson.

Approved by: core, peter, alc, rwatson
</content>
</entry>
<entry>
<title>Enforce the file size limit in VOP_WRITE() as well as VOP_TRUNCATE();</title>
<updated>2004-02-19T09:06:06Z</updated>
<author>
<name>Tim J. Robbins</name>
<email>tjr@FreeBSD.org</email>
</author>
<published>2004-02-19T09:06:06Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=3722550aa6a8e921bd05cc059a4f72951fb13c7e'/>
<id>urn:sha1:3722550aa6a8e921bd05cc059a4f72951fb13c7e</id>
<content type='text'>
pointed out by bde.
</content>
</entry>
<entry>
<title>Locking for the per-process resource limits structure.</title>
<updated>2004-02-04T21:52:57Z</updated>
<author>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</author>
<published>2004-02-04T21:52:57Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=91d5354a2ce810d848eca6ecf9da1027aeb2be6d'/>
<id>urn:sha1:91d5354a2ce810d848eca6ecf9da1027aeb2be6d</id>
<content type='text'>
- struct plimit includes a mutex to protect a reference count.  The plimit
  structure is treated similarly to struct ucred in that is is always copy
  on write, so having a reference to a structure is sufficient to read from
  it without needing a further lock.
- The proc lock protects the p_limit pointer and must be held while reading
  limits from a process to keep the limit structure from changing out from
  under you while reading from it.
- Various global limits that are ints are not protected by a lock since
  int writes are atomic on all the archs we support and thus a lock
  wouldn't buy us anything.
- All accesses to individual resource limits from a process are abstracted
  behind a simple lim_rlimit(), lim_max(), and lim_cur() API that return
  either an rlimit, or the current or max individual limit of the specified
  resource from a process.
- dosetrlimit() was renamed to kern_setrlimit() to match existing style of
  other similar syscall helper functions.
- The alpha OSF/1 compat layer no longer calls getrlimit() and setrlimit()
  (it didn't used the stackgap when it should have) but uses lim_rlimit()
  and kern_setrlimit() instead.
- The svr4 compat no longer uses the stackgap for resource limits calls,
  but uses lim_rlimit() and kern_setrlimit() instead.
- The ibcs2 compat no longer uses the stackgap for resource limits.  It
  also no longer uses the stackgap for accessing sysctl's for the
  ibcs2_sysconf() syscall but uses kernel_sysctl() instead.  As a result,
  ibcs2_sysconf() no longer needs Giant.
- The p_rlimit macro no longer exists.

Submitted by:	mtm (mostly, I only did a few cleanups and catchups)
Tested on:	i386
Compiled on:	alpha, amd64
</content>
</entry>
<entry>
<title>Spell magic '16' number as IO_SEQSHIFT.</title>
<updated>2004-01-19T20:03:43Z</updated>
<author>
<name>Alexander Kabaev</name>
<email>kan@FreeBSD.org</email>
</author>
<published>2004-01-19T20:03:43Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=6bd39fe97840366e063fc9383443bc0d3076df53'/>
<id>urn:sha1:6bd39fe97840366e063fc9383443bc0d3076df53</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove register keyword.</title>
<updated>2002-05-16T19:43:28Z</updated>
<author>
<name>Ian Dowse</name>
<email>iedowse@FreeBSD.org</email>
</author>
<published>2002-05-16T19:43:28Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=13a263882f04003890ada9178b16911fadc834c0'/>
<id>urn:sha1:13a263882f04003890ada9178b16911fadc834c0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Complete the separation of ext2fs from ufs by copying the remaining</title>
<updated>2002-05-16T19:08:03Z</updated>
<author>
<name>Ian Dowse</name>
<email>iedowse@FreeBSD.org</email>
</author>
<published>2002-05-16T19:08:03Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=9504abaad76b5fa631ac0eb7a59d107332189fbd'/>
<id>urn:sha1:9504abaad76b5fa631ac0eb7a59d107332189fbd</id>
<content type='text'>
shared code and converting all ufs references. Originally it may
have made sense to share common features between the two filesystems,
but recently it has only caused problems, the UFS2 work being the
final straw.

All UFS_* indirect calls are now direct calls to ext2_* functions,
and ext2fs-specific mount and inode structures have been introduced.
</content>
</entry>
<entry>
<title>KSE Milestone 2</title>
<updated>2001-09-12T08:38:13Z</updated>
<author>
<name>Julian Elischer</name>
<email>julian@FreeBSD.org</email>
</author>
<published>2001-09-12T08:38:13Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=b40ce4165d5eb3a5de1515245055350ae3dbab8e'/>
<id>urn:sha1:b40ce4165d5eb3a5de1515245055350ae3dbab8e</id>
<content type='text'>
Note ALL MODULES MUST BE RECOMPILED
make the kernel aware that there are smaller units of scheduling than the
process. (but only allow one thread per process at this time).
This is functionally equivalent to teh previousl -current except
that there is a thread associated with each process.

Sorry john! (your next MFC will be a doosie!)

Reviewed by: peter@freebsd.org, dillon@freebsd.org

X-MFC after:    ha ha ha ha
</content>
</entry>
<entry>
<title>Grab the process lock while calling psignal and before calling psignal.</title>
<updated>2001-03-07T03:37:06Z</updated>
<author>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</author>
<published>2001-03-07T03:37:06Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=19eb87d22a5314e238867d1e30894cc9dadf3ec4'/>
<id>urn:sha1:19eb87d22a5314e238867d1e30894cc9dadf3ec4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Proc locking, mostly protecting p_ucred while obtaining additional</title>
<updated>2001-01-23T22:41:15Z</updated>
<author>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</author>
<published>2001-01-23T22:41:15Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=157403fff063dd24d83076a7c48bcf82073cefd7'/>
<id>urn:sha1:157403fff063dd24d83076a7c48bcf82073cefd7</id>
<content type='text'>
references.
</content>
</entry>
<entry>
<title>Avoid a data-consistency race between write() and mmap()</title>
<updated>2000-12-17T23:57:05Z</updated>
<author>
<name>Matthew Dillon</name>
<email>dillon@FreeBSD.org</email>
</author>
<published>2000-12-17T23:57:05Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=6ddaf0f45e7b356053af082c8c7dac6b5b3312c6'/>
<id>urn:sha1:6ddaf0f45e7b356053af082c8c7dac6b5b3312c6</id>
<content type='text'>
by ensuring that newly allocated blocks are zerod.  The
race can occur even in the case where the write covers
the entire block.

Reported by: Sven Berkvens &lt;sven@berkvens.net&gt;, Marc Olzheim &lt;zlo@zlo.nu&gt;
</content>
</entry>
</feed>
