From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jens Axboe <axboe@kernel.dk>, Jan Kara <jack@suse.cz>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: [GIT PULL] Writeback fix
Date: Sat, 10 Dec 2022 09:44:16 -0800 [thread overview]
Message-ID: <CAHk-=wgqkWVi3nm6HJvOOy+GUVmPt9Wun+_ZVp47wZU43FET9w@mail.gmail.com> (raw)
In-Reply-To: <9f6a8d1a-aa05-626d-6764-99c376722ed7@kernel.dk>
On Sat, Dec 10, 2022 at 7:36 AM Jens Axboe <axboe@kernel.dk> wrote:
>
> Just a single writeback fix from Jan, for sanity checking adding freed
> inodes to lists.
That's what the commit message says too, but that's not what the patch
actually *does*.
It also does that unexplained
+ if (inode->i_state & I_FREEING) {
+ list_del_init(&inode->i_io_list);
+ wb_io_lists_depopulated(wb);
+ return;
+ }
that is new.
And yes, it has a link: in the commit message. And yes, I followed the
link in case it had some background.
And dammit, it's ANOTHER of those stupid pointless and worthless links
that just links to the patch submission, and has NO ADDITIONAL
INFORMATION.
Those links are actively detrimental. Stop it. I just wasted time
hoping that there would be some information about why the patch was
sent to me this late in the game. Instead, I just wated time on it.
I pulled this and then unpulled it. I'm very very annoyed. This patch
has an actively misleading commit message, has no explanation for why
it's so critical that it needs to be sent, and has a useless link to
garbage.
Fix the damn explanation to actually match the change. Fix the damn
link to point to something *useful* like the error report or
something.
And STOP WASTING EVERYBODY'S TIME with these annoying links that I
keep hoping would explain something and give useful background to the
change and instead just are a source of constant disappointment.
Linus
next prev parent reply other threads:[~2022-12-10 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 15:36 Jens Axboe
2022-12-10 17:44 ` Linus Torvalds [this message]
2022-12-10 18:11 ` Jens Axboe
2022-12-10 18:14 ` Linus Torvalds
2022-12-10 18:56 ` Jens Axboe
2022-12-12 11:33 ` Jan Kara
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='CAHk-=wgqkWVi3nm6HJvOOy+GUVmPt9Wun+_ZVp47wZU43FET9w@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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