lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166450797714.256913.16618397949640055168.b4-ty@mit.edu>
Date:   Thu, 29 Sep 2022 23:19:35 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     adilger.kernel@...ger.ca, hanjinke.666@...edance.com
Cc:     "Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org,
        linux-kernel@...r.kernel.org, yi.zhang@...wei.com
Subject: Re: [PATCH v2] ext4: place buffer head allocation before handle start

On Sat, 3 Sep 2022 09:24:29 +0800, Jinke Han wrote:
> From: Jinke Han <hanjinke.666@...edance.com>
> 
> In our product environment, we encounter some jbd hung waiting handles to
> stop while several writters were doing memory reclaim for buffer head
> allocation in delay alloc write path. Ext4 do buffer head allocation with
> holding transaction handle which may be blocked too long if the reclaim
> works not so smooth. According to our bcc trace, the reclaim time in
> buffer head allocation can reach 258s and the jbd transaction commit also
> take almost the same time meanwhile. Except for these extreme cases,
> we often see several seconds delays for cgroup memory reclaim on our
> servers. This is more likely to happen considering docker environment.
> 
> [...]

Applied, thanks!

[1/1] ext4: place buffer head allocation before handle start
      commit: 843b6ee4b8d0d9e7507dad491920db1fbde12439

Best regards,
-- 
Theodore Ts'o <tytso@....edu>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ