Date: Sun, 24 Feb 2002 12:04:34 -0700 From: "Justin T. Gibbs" <gibbs@scsiguy.com> To: Matt Dillon <dillon@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_shutdown.c Message-ID: <200202241904.g1OJ4YI78683@aslan.scsiguy.com> In-Reply-To: Your message of "Thu, 21 Feb 2002 11:15:10 PST." <200202211915.g1LJFAi09419@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>dillon 2002/02/21 11:15:10 PST > > Modified files: (Branch: RELENG_4) > sys/kern kern_shutdown.c > Log: > If a system shutdown is performed immediately after doing softupdates-heavy > filesystem operations the shutdown code may stall on buffers being held > locked by softupdates, resulting an unclean shutdown. These buffers are > never unlocked because the syncer has already been killed. The solution is > to call bioops.io_sync() in the shutdown code. Hmm. Can't this be handled in some more generic fashion? I can't believe that the syncer is the only "special process" that may want to clean things up during shutdown. I suppose we don't kill it off by trying to SIGTERM (or some equivalent) it first? A generic mechanism would allow the special behavior to be localized to the area needing it instead (and where that behavior might change) rather than in the middle of the generic shutdown code. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200202241904.g1OJ4YI78683>