linux-kernel - Re: 2.6.29 -mm merge plans

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 7 Jan 2009 04:28:03 +0100
From:	Nick Piggin <npiggin@...e.de>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.29 -mm merge plans

On Wed, Jan 07, 2009 at 03:57:25AM +0100, Andi Kleen wrote:
> > sys_sync B which is invoked *after* sys_sync caller A should not
> > return before A. If you didn't have a global lock, they'd tend to
> > block one another's pages anyway. I think it's OK.
> 
> It means that you cannot reboot because reboot does sync.
> What happens when the sync gets stuck somewhere on a really
> slow device?

I don't follow you.

The sync gets "stuck" because it is writing out dirty data. You
don't want to reboot before that happens, which is exactly the
reason why sync gets called (although it is probably not needed
anyway if all filesystems get unmounted).

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/