<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/vm, branch releng/12.4</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=releng%2F12.4</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=releng%2F12.4'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2022-08-09T19:46:38Z</updated>
<entry>
<title>vm_fault: Shoot down shared mappings in vm_fault_copy_entry()</title>
<updated>2022-08-09T19:46:38Z</updated>
<author>
<name>Mark Johnston</name>
<email>markj@FreeBSD.org</email>
</author>
<published>2022-07-25T20:53:21Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=9a2a2871c4908cfe7012236912918622e0ed0b32'/>
<id>urn:sha1:9a2a2871c4908cfe7012236912918622e0ed0b32</id>
<content type='text'>
As in vm_fault_cow(), it's possible, albeit rare, for multiple vm_maps
to share a shadow object.  When copying a page from a backing object
into the shadow, all mappings of the source page must therefore be
removed.  Otherwise, future operations on the object tree may detect
that the source page is fully shadowed and thus can be freed.

Approved by:	so
Security:	FreeBSD-SA-22:11.vm
Reviewed by:	alc, kib
Sponsored by:	The FreeBSD Foundation
Differential Revision:	https://reviews.freebsd.org/D35635

(cherry picked from commit 5c50e900ad779fccbf0a230bfb6a68a3e93ccf60)
</content>
</entry>
<entry>
<title>vm: Fix a common typo in a source code comment</title>
<updated>2022-06-10T12:42:39Z</updated>
<author>
<name>Gordon Bergling</name>
<email>gbe@FreeBSD.org</email>
</author>
<published>2022-06-05T07:52:32Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=ad8d15eec1a3f558f12c3991ec256dac79938aeb'/>
<id>urn:sha1:ad8d15eec1a3f558f12c3991ec256dac79938aeb</id>
<content type='text'>
- s/independant/independent/

(cherry picked from commit 860740ae0f0f247b2dabd15fcfa0c215f77e5858)
</content>
</entry>
<entry>
<title>vm_page: Fix a typo in a source code comment</title>
<updated>2022-06-10T12:38:16Z</updated>
<author>
<name>Gordon Bergling</name>
<email>gbe@FreeBSD.org</email>
</author>
<published>2022-06-04T10:52:22Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=3eecab672f03e26c95e452215e87da14e1622f3d'/>
<id>urn:sha1:3eecab672f03e26c95e452215e87da14e1622f3d</id>
<content type='text'>
- s/consistancy/consistency/

(cherry picked from commit f77a88c855c557902e4e4c9696b08e847c413f54)
</content>
</entry>
<entry>
<title>memguard(9): Fix two typos in source code comments</title>
<updated>2022-04-09T06:29:54Z</updated>
<author>
<name>Gordon Bergling</name>
<email>gbe@FreeBSD.org</email>
</author>
<published>2022-04-02T11:51:27Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=944d201a2a38a4579ac21a19b5e660a95d50d635'/>
<id>urn:sha1:944d201a2a38a4579ac21a19b5e660a95d50d635</id>
<content type='text'>
- s/comparsion/comparison/

(cherry picked from commit f167c46e7965ae08255313c4a624be19b4873442)
</content>
</entry>
<entry>
<title>vm_reserv: fix zero-boundary error</title>
<updated>2021-12-29T17:28:13Z</updated>
<author>
<name>Doug Moore</name>
<email>dougm@FreeBSD.org</email>
</author>
<published>2021-12-26T17:40:27Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=53dd5ccce2ac3bc8914d8c6d7dede927887503d9'/>
<id>urn:sha1:53dd5ccce2ac3bc8914d8c6d7dede927887503d9</id>
<content type='text'>
Handle specially the boundary==0 case of vm_reserv_reclaim_config,
by turning off boundary adjustment in that case.

Reviewed by:	alc
Tested by:	pho, madpilot

(cherry picked from commit 49fd2d51f07fb29af3fd239f83f249c00cd84123)
(cherry picked from commit dd8ea1c755b3cc2c9c4eaa8611a97ac8f0f9b755)
</content>
</entry>
<entry>
<title>Correct type size format error in KASSERT.</title>
<updated>2021-12-23T08:05:18Z</updated>
<author>
<name>Doug Moore</name>
<email>dougm@FreeBSD.org</email>
</author>
<published>2021-12-16T19:48:58Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=39816676b6c6a461ed8bcf9311058054383a82db'/>
<id>urn:sha1:39816676b6c6a461ed8bcf9311058054383a82db</id>
<content type='text'>
Reported by:	jenkins
Fixes:	6f1c8908272f vm: Don't break vm reserv that can't meet align reqs

(cherry picked from commit f7aa44763d20d06c9ea5caf330aca02a8b107a70)
</content>
</entry>
<entry>
<title>vm: Don't break vm reserv that can't meet align reqs</title>
<updated>2021-12-23T08:04:53Z</updated>
<author>
<name>Doug Moore</name>
<email>dougm@FreeBSD.org</email>
</author>
<published>2021-12-16T18:20:56Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=46549e319c5257c1305d78930b81ef022fa2e178'/>
<id>urn:sha1:46549e319c5257c1305d78930b81ef022fa2e178</id>
<content type='text'>
Function vm_reserv_test_contig has incorrectly used its alignment
and boundary parameters to find a well-positioned range of empty pages
in a reservation.  Consequently, a reservation could be broken
mistakenly when it was unable to provide a satisfactory set of pages.

Rename the function, correct the errors, and add assertions to detect
the error in case it appears again.

Reviewed by:	alc, markj
MFC after:	1 week
Differential Revision:	https://reviews.freebsd.org/D33344

(cherry picked from commit 6f1c8908272f3c0a6631e001bd2eb50a5b69261d)
</content>
</entry>
<entry>
<title>Set uninitialized popmap bits in vm_reserv_init</title>
<updated>2021-12-14T05:14:40Z</updated>
<author>
<name>Doug Moore</name>
<email>dougm@FreeBSD.org</email>
</author>
<published>2021-12-05T23:17:25Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=434b8658dc8d5d42071814c42fb6d940dfc76972'/>
<id>urn:sha1:434b8658dc8d5d42071814c42fb6d940dfc76972</id>
<content type='text'>
In vm_reserv_init, set all the marker popmap bits in vm_reserv_init,
and not just the bits of the first popmap entry.

Reviewed by:	markj
MFC after:	1 week
Differential Revision:	https://reviews.freebsd.org/D33258

(cherry picked from commit 9f32cb5b1c81ceed28491c031cd109811a5f5d7a)
</content>
</entry>
<entry>
<title>loader: create single zfs nextboot implementation</title>
<updated>2021-10-08T05:24:20Z</updated>
<author>
<name>Toomas Soome</name>
<email>tsoome@FreeBSD.org</email>
</author>
<published>2020-06-20T06:23:31Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=7313f59b868025caa34453591e5d24cd75cd9076'/>
<id>urn:sha1:7313f59b868025caa34453591e5d24cd75cd9076</id>
<content type='text'>
We should have nextboot feature implemented in libsa zfs code.
To get there, I have created zfs_nextboot() implementation based on
two sources, our current simple textual string based approach with added
structured boot label PAD structure from OpenZFS.

Secondly, all nvlist details are moved to separate source file and
restructured a bit. This is done to provide base support to add nvlist
add/update feature in followup updates.

And finally, the zfsboot/gptzfsboot disk access functions are swapped to
use libi386 and libsa.

(cherry picked from commit 3830659e99640001c09d26dfc0e1bbd77d919a62)
(cherry picked from commit a137f7997efc8a34da75a7643c8fade4be67e82c)
(cherry picked from commit 4583682ec14cc63f063b6769b7706af1891b0934)
</content>
</entry>
<entry>
<title>Fix a few typos in source code comments</title>
<updated>2021-08-19T07:31:24Z</updated>
<author>
<name>Gordon Bergling</name>
<email>gbe@FreeBSD.org</email>
</author>
<published>2021-08-14T07:06:09Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=b26056a6bd68fab3e083d0fa1ad8a49de787b20e'/>
<id>urn:sha1:b26056a6bd68fab3e083d0fa1ad8a49de787b20e</id>
<content type='text'>
- s/becase/because/

(cherry picked from commit fa7a635f7ee277960eb37b9102a3aef76b36b825)
</content>
</entry>
</feed>
