From: Edward Shishkin <edward.shishkin@gmail.com>
To: Metztli Information Technology <jose.r.r@metztli.com>,
reiserfs-devel@vger.kernel.org
Subject: Re: reiser4 patch for 5.5.1 and fs/fs-writeback.c
Date: Sat, 22 Feb 2020 12:56:16 +0100 [thread overview]
Message-ID: <6e90d853-593c-223a-c529-1f8724907bbe@gmail.com> (raw)
In-Reply-To: <20200222045124.740D350BE086@huitzilopochtli.metztli-it.com>
On 02/22/2020 05:51 AM, Metztli Information Technology wrote:
> Niltze, Ed-
>
> Starting with kernel 5.4.19, linux/fs/fs-writeback.c , at line 2066, changes
> from
> set_worker_desc("flush-%s", dev_name(wb->bdi->dev));
>
> to
> set_worker_desc("flush-%s", bdi_dev_name(wb->bdi));
>
> I realized that when I was hacking 5.4.19 and, subsequently, my currently running kernel --as there was no RC3:
>
> uname -a
> Linux huitzilopochtli 5.4.0-4+reiser4.0.2-amd64 #1 SMP Debian 5.4.20-1+reiser4.0.2 (2020-02-14) x86_64 GNU/Linux
>
> < https://sourceforge.net/projects/metztli-reiser4/files/Reiser4-SFRN-4.0.2_Linux-5.4.20-1-RC2_for-Debian_Buster/ >
>
>
> I have just built 5.5.5-1 and realized, upon applying reiser4-for-5.5.1.patch.gz, that your patch should be modified
> accordingly; else, the patch will fail and will necessitate manual intervention, i.e., similar to 5.4.18 vs 5.4.19:
>
> < https://metztli.it/readOnlyEphemeral/fs-writeback_c.png >
so, everything works fine after that "manual intervention"?
next prev parent reply other threads:[~2020-02-22 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 4:51 reiser4 patch for 5.5.1 and fs/fs-writeback.c Metztli Information Technology
2020-02-22 11:56 ` Edward Shishkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-22 19:34 Metztli Information Technology
2020-02-22 21:57 ` Edward Shishkin
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=6e90d853-593c-223a-c529-1f8724907bbe@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=jose.r.r@metztli.com \
--cc=reiserfs-devel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).