PR/60531 CVS commit: [netbsd-11] src/sys/kern
"Martin Husemann" <[email protected]>
| Newsgroups | gmane.os.netbsd.bugs |
|---|---|
| Message-ID | <[email protected]> |
The following reply was made to PR kern/60531; it has been noted by GNATS. From: "Martin Husemann" <[email protected]> To: [email protected] Cc: Subject: PR/60531 CVS commit: [netbsd-11] src/sys/kern Date: Mon, 17 Aug 2026 15:47:55 +0000 Module Name: src Committed By: martin Date: Mon Aug 17 15:47:55 UTC 2026 Modified Files: src/sys/kern [netbsd-11]: vfs_subr.c Log Message: Pull up following revision(s) (requested by riastradh in ticket #415): sys/kern/vfs_subr.c: revision 1.504 vflushbuf: Print `vflushbuf: dirty' warning only once per call. And do it only under DEBUG, and rate-limit it globally. This can happen when vflushbuf is competing with an onslaught of concurrent I/O on a snapshot or block device (which is done without holding the vnode lock, despite what the comment says). That concurrent I/O might be happening indefinitely, so we are likely to have to print a _lot_ of warnings, potentially overwhelming the console, until the underlying problem is fixed by teaching vflushbuf to wait only for the writes that began before have completed, not also all writes that have begun since. This stop-gap measure intended to be low-risk for pullup to release branches. PR kern/60531: looping "vflushbuf: dirty" message To generate a diff of this commit: cvs rdiff -u -r1.502.2.1 -r1.502.2.2 src/sys/kern/vfs_subr.c Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files.