[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090107025725.GJ496@one.firstfloor.org>
Date: Wed, 7 Jan 2009 03:57:25 +0100
From: Andi Kleen <andi@...stfloor.org>
To: Nick Piggin <npiggin@...e.de>
Cc: Andi Kleen <andi@...stfloor.org>,
Christoph Hellwig <hch@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: 2.6.29 -mm merge plans
> 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?
-Andi
--
ak@...ux.intel.com
--
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/
Powered by blists - more mailing lists