From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Joshua Hudson <joshudson@gmail.com>, Al Viro <viro@zeniv.linux.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux IDE and libata <linux-ide@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>, Jens Axboe <axboe@kernel.dk>,
Damien Le Moal <dlemoal@kernel.org>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Subject: Re: Cache coherency bug: stale reads on /dev/sda1
Date: Sun, 27 Aug 2023 09:50:46 +0700 [thread overview]
Message-ID: <e644366b-8387-c228-78cb-f108453b0b1d@gmail.com> (raw)
In-Reply-To: <CA+jjjYRr3SHvXhVZLfACkUrN98n3W8aMBe1e8zqUNDuRZt17=A@mail.gmail.com>
On 27/08/2023 09:38, Joshua Hudson wrote:
> "Whole disk and all partitions have page caches of their own."
>
> That's so bad.
>
> I can think of numerous cases where this will cause problems; including
> some I encountered last year and did not understand at the time. Manipulating
> EFI partitions through the whole disk device makes sense because FAT filesystems
> *know their offset on the disk*, and some of the existing tools really
> don't like being
> given a partition device.
>
> There's also the astounding: write stuff to disk, umount everything,
> copy one disk to
> another using the whole disk device doesn't work because reading the whole disk
> yields a stale cache (sometimes).
>
> On the other hand, I can think of very few cases where the file vs
> disk buffer pool
> matters, because the loop device is unaffected (writing to a loop
> block device is
> coherent with the file).
>
tl;dr:
> A: http://en.wikipedia.org/wiki/Top_post
> Q: Were do I find info about this thing called top-posting?
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
> A: No.
> Q: Should I include quotations after my reply?
>
> http://daringfireball.net/2007/07/on_top
What cases on the loop devices?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-08-27 2:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 21:59 Joshua Hudson
2023-08-27 1:03 ` Bagas Sanjaya
2023-08-27 1:25 ` Joshua Hudson
2023-08-27 2:06 ` Al Viro
2023-08-27 2:38 ` Joshua Hudson
2023-08-27 2:50 ` Bagas Sanjaya [this message]
2023-08-27 4:17 ` Al Viro
2023-08-27 14:39 ` Joshua Hudson
2023-08-27 16:30 ` Al Viro
2023-08-27 18:33 ` Joshua Hudson
2023-09-06 7:42 ` Hannes Reinecke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e644366b-8387-c228-78cb-f108453b0b1d@gmail.com \
--to=bagasdotme@gmail.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=hdegoede@redhat.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=joshudson@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®