src/sys/dev/md, branch releng/14.2FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=releng%2F14.22024-10-20T00:33:04Zmd(4): always trim the last partial sector2024-10-20T00:33:04ZKonstantin Belousovkib@FreeBSD.org2024-10-13T21:28:22Zurn:sha1:959f0d0cdb1482d754f24b7ae16bda0ac2e7b31a
PR: 281978
(cherry picked from commit 4bf34c597c44a2393ac5ec483e9cecac128d8202)
md: round-trip the MUSTDEALLOC and RESERVE options2024-06-15T13:03:23ZAlan Somersasomers@FreeBSD.org2024-06-01T18:00:03Zurn:sha1:35e9830283561820a1fcb21b46b6f01e87700dec
If those options are requested when the device is created, ensure that
they will be reported by MDIOCQUERY.
Reviewed by: imp
Pull Request: https://github.com/freebsd/freebsd-src/pull/1270
(cherry picked from commit 9d449caddd4f442ba4ebfd2edafa1aef4fcba4c8)
sys: Remove $FreeBSD$: two-line .h pattern2023-08-16T17:54:11ZWarner Loshimp@FreeBSD.org2023-08-16T17:54:11Zurn:sha1:95ee2897e98f5d444f26ed2334cc7c439f9c16c6
Remove /^\s*\*\n \*\s+\$FreeBSD\$$\n/
md driver compat32: fix structure padding for arm, powerpc2023-08-08T14:09:03ZMike Karelskarels@FreeBSD.org2023-08-08T14:09:03Zurn:sha1:58a46cfd751ac726ddca8544bf73a290b0154a57
Because the 32-bit md_ioctl structure contains 64-bit members, arm
and powerpc add padding to a multiple of 8. i386 doesn't do this.
The md_ioctl32 definition was correct for amd64/i386 without padding,
but wrong for arm64 and powerpc64. Make __packed__ conditional on
__amd64__, and test for the expected size on non-amd64. Note that
mdconfig is used in the ATF test suite. Note, I verified the
structure size for powerpc, but was unable to test.
MFC after: 1 week
Reviewed by: jrtc27
Differential Revision: https://reviews.freebsd.org/D41339
Discussed with: jhibbits
Pre-quote macros passed to .incbin to avoid unwanted substitution2023-07-28T04:08:43ZJessica Clarkejrtc27@FreeBSD.org2023-07-28T04:08:43Zurn:sha1:8a6ab0f71f1857037233fae19991b972b430d83c
Currently for the MFS, firmware and VDSO template assembly files we pass
the path to include with .incbin unquoted and use __XSTRING within the
assembly file to stringify it. However, __XSTRING doesn't just perform a
single level of expansion, it performs the normal full expansion of the
macro, and so if the path itself happens to tokenise to something that
includes a defined macro in it that will itself be substituted. For
example, with #define MACRO 1, a path like /path/containing/MACRO/in/it
will expand to /path/containing/1/in/it and then, when stringified, end
up as "/path/containing/1/in/it", not the intended string. Normally,
macros have names that start or end witih underscores and are unlikely
to appear in a tokenised path (even if technically they could), but now
that we've switched to GNU C as of commit ec41a96daaa6 ("sys: Switch the
kernel's C standard from C99 to GNU99.") there are a few new macros
defined which don't start or end with underscores: unix, which is always
defined to 1, and i386, which is defined to 1 on i386. The former
probably doesn't appear in user paths in practice, but the latter has
been seen to and is likely quite common in the wild.
Fix this by defining the macro pre-quoted instead of using __XSTRING.
Note that technically we don't need to do this for vdso_wrap.S today as
all the paths passed to it are safe file names with no user-controlled
prefix but we should do it anyway for consistency and robustness against
future changes.
This allows make tinderbox to pass when built with source and object
directories inside ~/path-with-unix, which would otherwise expand to
~/path-with-1 and break.
PR: 272744
Fixes: ec41a96daaa6 ("sys: Switch the kernel's C standard from C99 to GNU99.")
md: Get rid of the pbuf zone2023-05-23T14:27:10ZMark Johnstonmarkj@FreeBSD.org2023-05-23T14:14:06Zurn:sha1:30038a8b4efc6d0b9f8f295e28bc205fe9728310
The zone is used solely to provide KVA for mapping BIOs so that we can
pass mapped buffers to VOP_READ and VOP_WRITE. Currently we preallocate
nswbuf/10 bufs for this purpose during boot.
The intent was to limit KVA usage on 32-bit systems, but the
preallocation means that we in fact consumed more KVA than needed unless
one has more than nswbuf/10 (typically 25) vnode-backed MD devices
in existence, which I would argue is the uncommon case.
Meanwhile, all I/O to an MD is handled by a dedicated thread, so we can
instead simply preallocate the KVA region at MD device creation time.
Event: BSDCan 2023
Reviewed by: kib
MFC after: 1 month
Differential Revision: https://reviews.freebsd.org/D40215
md.c: another style fix2023-01-20T02:39:36ZKonstantin Belousovkib@FreeBSD.org2023-01-20T02:39:36Zurn:sha1:ad8feb1ed9996593df8b4b7259057c6e263aa130
Noted by: jkim
Sponsored by: The FreeBSD Foundation
MFC after: 3 days
Handle ERELOOKUP from VOP_FSYNC() in several other places2023-01-20T01:54:56ZKonstantin Belousovkib@FreeBSD.org2023-01-18T21:09:10Zurn:sha1:6189672e600814fec4cc165d25ae050fb2f3a999
We need to repeat the operation if the vnode was relocked.
Reported and reviewed by: markj
Tested by: pho
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Differential revision: https://reviews.freebsd.org/D38114
vfs: NDFREE(&nd, NDF_ONLY_PNBUF) -> NDFREE_PNBUF(&nd)2022-03-24T10:20:51ZMateusz Guzikmjg@FreeBSD.org2022-03-24T10:10:03Zurn:sha1:bb92cd7bcd16f3f36cdbda18d8193619892715fbmd(4): Add dummy support of the BIO_FLUSH command for malloc and swap2022-02-17T19:21:56ZAleksandr Fedorovafedorov@FreeBSD.org2022-02-17T19:21:56Zurn:sha1:cb28dfb27d12f1cbd7831f370c01493c01d74b10
backend.
PR: 260200
Reported by: editor@callfortesting.org
Reviewed by: vmaffione (mentor), markj
Approved by: vmaffione (mentor), markj
Differential Revision: https://reviews.freebsd.org/D34260