From: David Howells <dhowells@redhat.com>
To: Max Kellermann <mk@cm4all.com>
Cc: dhowells@redhat.com, linux-cachefs@redhat.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: fscache corruption in Linux 5.17?
Date: Tue, 19 Apr 2022 16:56:48 +0100 [thread overview]
Message-ID: <507518.1650383808@warthog.procyon.org.uk> (raw)
In-Reply-To: <YlWWbpW5Foynjllo@rabbit.intern.cm-ag>
Max Kellermann <mk@cm4all.com> wrote:
> - * For these first content media elements, the `loading` attribute will be omitted. By default, this is the case
> + * For these first content media elements, the `loading` efault, this is the case
> * for only the very first content media element.
> *
> * @since 5.9.0
> @@ -5377,3 +5377,4 @@
>
> return $content_media_count;
> }
> +^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
This is weird. It looks like content got slid down by 31 bytes and 31 zero
bytes got added at the end. I'm not sure how fscache would achieve that -
nfs's implementation should only be dealing with pages.
David
next prev parent reply other threads:[~2022-04-19 15:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 15:10 fscache corruption in Linux 5.17? Max Kellermann
2022-04-16 11:38 ` Thorsten Leemhuis
2022-04-16 19:55 ` Max Kellermann
2022-04-19 13:02 ` David Howells
2022-04-19 14:18 ` Max Kellermann
2022-04-19 15:23 ` [Linux-cachefs] " David Wysochanski
2022-04-19 16:17 ` David Howells
2022-04-19 16:41 ` Max Kellermann
2022-04-19 16:47 ` David Howells
2022-04-19 15:56 ` David Howells [this message]
2022-04-19 16:06 ` Max Kellermann
2022-04-19 16:42 ` David Howells
2022-04-19 18:01 ` Max Kellermann
2022-04-19 21:27 ` Max Kellermann
2022-04-20 13:55 ` David Howells
2022-05-04 8:38 ` Max Kellermann
2022-05-31 8:35 ` David Howells
2022-05-31 8:41 ` Max Kellermann
2022-05-31 9:13 ` David Howells
2022-06-20 7:11 ` Thorsten Leemhuis
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=507518.1650383808@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mk@cm4all.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.