| 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
| ||
|
Message-ID: <CA+3zgmsC2qKph_wDfknSa5eq6EnJqxzzj4K7G4_ZxGr5ZQTqbA@mail.gmail.com> Date: Tue, 20 Jun 2023 09:25:52 -0400 From: Tim Lewis <elatllat@...il.com> To: osmtendev@...il.com, Greg KH <gregkh@...uxfoundation.org> Cc: open list <linux-kernel@...r.kernel.org>, stable@...r.kernel.org Subject: Re: [PATCH 5.10 00/89] 5.10.185-rc1 review Is it intentional and acceptable for dmesg to now log 14 "Failed to create debugfs directory" messages? I assume it's related to "regulator: Fix error checking for debugfs_create_dir". dmesg 398 lines: diff ./5.10.184-rc1-dirty.txt ./5.10.185-rc1-dirty.txt 19a20 > 12V: Failed to create debugfs directory 20a22 > 5V: Failed to create debugfs directory 69a72 > FLASH_1V8: Failed to create debugfs directory 72a76 > HUB_5V: Failed to create debugfs directory 121a126,127 > TFLASH_VDD: Failed to create debugfs directory > TF_IO: Failed to create debugfs directory 122a129 > USB_PWR_EN: Failed to create debugfs directory 123a131 > VCC_1V8: Failed to create debugfs directory 124a133 > VCC_3V3: Failed to create debugfs directory 125a135 > VDDAO_1V8: Failed to create debugfs directory 126a137 > VDDAO_3V3: Failed to create debugfs directory 127a139 > VDDCPU: Failed to create debugfs directory 278a291,292 > regulator-dummy: Failed to create debugfs directory > regulator: Failed to create debugfs directory kselftest 270 tests: diff ./out_5.10.184-rc1-dirty.txt ./out_5.10.185-rc1-dirty.txt ltp 865 tests: diff ./out_5.10.184-rc1-dirty.txt ./out_5.10.185-rc1-dirty.txt
Powered by blists - more mailing lists