linux-ext4 - Re: [PATCH] ext4: Fix journal_ioprio mount option handling

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: <165249378801.644521.15436473858156116983.b4-ty@mit.edu>
Date:   Fri, 13 May 2022 22:03:15 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     Ojaswin Mujoo <ojaswin@...ux.ibm.com>, linux-ext4@...r.kernel.org
Cc:     "Theodore Ts'o" <tytso@....edu>, linux-fsdevel@...r.kernel.org,
        Ritesh Harjani <riteshh@...ux.ibm.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ext4: Fix journal_ioprio mount option handling

On Mon, 18 Apr 2022 14:05:45 +0530, Ojaswin Mujoo wrote:
> In __ext4_super() we always overwrote the user specified journal_ioprio
> value with a default value, expecting  parse_apply_sb_mount_options() to
> later correctly set ctx->journal_ioprio to the user specified value.
> However, if parse_apply_sb_mount_options() returned early because of
> empty sbi->es_s->s_mount_opts, the correct journal_ioprio value was
> never set.
> 
> [...]

Applied, thanks!

[1/1] ext4: Fix journal_ioprio mount option handling
      commit: 8d7b9890b5d18a593b7c7e10d23513340919b837

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