From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 50981] ext4 : DATA CORRUPTION read and write on same 4096 page
range
Date: Mon, 26 Nov 2012 11:18:39 +0000 (UTC)
Message-ID: <20121126111839.1E5D011FB81@bugzilla.kernel.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
To: linux-ext4@vger.kernel.org
Return-path:
Received: from mail.kernel.org ([198.145.19.201]:37148 "EHLO mail.kernel.org"
rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
id S1754552Ab2KZLSp (ORCPT );
Mon, 26 Nov 2012 06:18:45 -0500
Received: from mail.kernel.org (localhost [127.0.0.1])
by mail.kernel.org (Postfix) with ESMTP id 72D9920136
for ; Mon, 26 Nov 2012 11:18:40 +0000 (UTC)
Received: from bugzilla.kernel.org (bugzilla.kernel.org [198.145.19.217])
by mail.kernel.org (Postfix) with ESMTP id 76A3420124
for ; Mon, 26 Nov 2012 11:18:39 +0000 (UTC)
In-Reply-To:
Sender: linux-ext4-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=50981
--- Comment #5 from Zheng Liu 2012-11-26 11:18:38 ---
(In reply to comment #4)
> Yes, that's what I said XFS has its own read/write exclusion. However we're
> reading/writing a single page here and page read/write shoud be atomic so we
> should _not_ see page with mixed data. Basically the page should be locked when
> we copy data from/to it,
Sorry, as my understanding, a page won't be locked when it is accessed if it
has been mark uptodate. If we write a page that has been written recently, the
uptodate flag won't be clear. So reader won't try to lock page, and maybe that
is not atomic. Am I missing something?
Regards,
Zheng
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.