linux-kernel - Fwd: bbbf096ea227607cbb348155eeda7af71af1a35b results in "dirty" shutdown

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-next>] [day] [month] [year] [list]

Message-ID: <cd397c88-bf53-4768-9ab8-9d107df9e613@gmail.com>
Date:   Wed, 25 Oct 2023 07:40:11 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Regressions <regressions@...ts.linux.dev>,
        Linux IDE and libata <linux-ide@...r.kernel.org>
Cc:     Damien Le Moal <dlemoal@...nel.org>,
        Hannes Reinecke <hare@...e.de>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        Tejun Heo <tj@...nel.org>,
        Totallyreal Name <kotversuchung@...il.com>,
        loqs <kernel_bugzilla@...ropy-collector.net>
Subject: Fwd: bbbf096ea227607cbb348155eeda7af71af1a35b results in "dirty"
 shutdown

Hi,

I notice a regression report on Bugzilla that seems to have been
handled already there [1]. Quoting from it:

> I have noticed that after each shutdown SMART would log +1 on each raw_value of drives that count power related issues.
> 
> Here are some of the smart values where i noticed increase among different drives
> 
> POR_Recovery_Count 
> Unexpect_Power_Loss_Ct  
> Power-Off_Retract_Count 
> 
> That doesn't happen on previous Kernels.. and it stops as soon as i switch back to LTS.
> I seeked through the Bug Reports but couldn't really find the issue. So i don't know if this has been reported or patched already.

Another reporter had found the culprit:

> 
> 
> This has been reported as being introduced in stable 6.5.8 [1].  Reverting commit 	bbbf096ea227607cbb348155eeda7af71af1a35b is reported to solve the issue [2]. bbbf096ea227607cbb348155eeda7af71af1a35b [3] is mainline commit aa3998dbeb3abce63653b7f6d4542e7dcd022590 [4] which was introduced in 6.6-rc4 which matches the original report.
> 
> [1]: https://bugs.archlinux.org/task/80064
> [2]: https://bugs.archlinux.org/task/80064#comment223100
> [3]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bbbf096ea227607cbb348155eeda7af71af1a35b
> [4]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa3998dbeb3abce63653b7f6d4542e7dcd022590

See Bugzilla for the full thread.

Anyway, I'm adding this regression to regzbot:

#regzbot introduced: aa3998dbeb3abc https://bugzilla.kernel.org/show_bug.cgi?id=218038
#regzbot title: dirty shutdown due to disabling manage_system_start_stop on SCSI devices
#regzbot link: https://bugs.archlinux.org/task/80064

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=218038

-- 
An old man doll... just what I always wanted! - Clara