From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 201461] ext4 journal stalls write system call
Date: Thu, 18 Oct 2018 14:22:47 +0000 [thread overview]
Message-ID: <bug-201461-13602-ygWJmWSVby@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201461-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201461
zhenbianshu@foxmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #6 from zhenbianshu@foxmail.com ---
(In reply to Theodore Tso from comment #5)
> Keep in mind that 3.10 was released over ***five years*** ago. Quite
> frankly, using a 3.10 kernel borders on malpractice, since it has so many
> unpatched security holes it isn't funny. If you are talking about a RHEL
> kernel, it has diverged significantly from mainline and whether or not it is
> a security disaster is between you and your Red Hat support contract. :-)
>
> My comments apply mainly to the the upstream development kernel, but to
> answer your questions:
>
> No, in 3.10, generic_writepages() does not call ext4_da_writepages(). And
> ext4_da_writepages roughly corresponds to what ext4_writepages() in
> non-obsolete kernels.
>
> A huge number of things have changed between 3.10 and more modern kernels,
> including many performance enhancements. So some of the details have
> changed.
I got it, thank you very much!
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2018-10-18 22:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 12:56 [Bug 201461] New: ext4 journal stalls write system call bugzilla-daemon
2018-10-17 12:57 ` [Bug 201461] " bugzilla-daemon
2018-10-17 15:39 ` bugzilla-daemon
2018-10-18 2:02 ` bugzilla-daemon
2018-10-18 2:35 ` bugzilla-daemon
2018-10-18 13:04 ` bugzilla-daemon
2018-10-18 14:12 ` bugzilla-daemon
2018-10-18 14:22 ` bugzilla-daemon [this message]
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=bug-201461-13602-ygWJmWSVby@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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