linux-kernel - Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues"

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

Date:   Sat, 1 Oct 2022 10:30:22 +0000
From:   "Artem S. Tashkinov" <aros@....com>
To:     Thorsten Leemhuis <linux@...mhuis.info>,
        Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc:     workflows@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        Greg KH <gregkh@...uxfoundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
        ksummit@...ts.linux.dev
Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla
 blues"

Here are two other issues which absolutely suck in terms of dealing with
the kernel.

- 1 -

I have a 20+ years experience in IT and some kernel issues are just
baffling in terms of trying to understand what to do about them.

Here's an example: https://bugzilla.kernel.org/show_bug.cgi?id=216274

What should I do about that? Who's responsible for this? Who should I CC?

And this is an issue which is easy to describe and identify.

- 2 -

Here's another one which is outright puzzling:

You run: dmesg -t --level=emerg,crit,err

And you see some non-descript errors of some kernel subsystems seemingly
failing or being unhappy about your hardware. Errors are as cryptic as
humanly possible, you don't even know what part of kernel has produced them.

OK, as a "power" user I download the kernel source, run `grep -R message
/tmp/linux-5.19` and there are _multiple_ different modules and places
which contain this message.

I'm lost. Send this to LKML? Did that in the long past, no one cared, I
stopped.

Here's what I'm getting with Linux 5.19.12:

platform wdat_wdt: failed to claim resource 5: [mem
0x00000000-0xffffffff7fffffff]
ACPI: watchdog: Device creation failed: -16
ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.PCI0.XHC.RHUB.TPLD], AE_NOT_FOUND (20220331/psargs-330)
ACPI Error: Aborting method \_SB.UBTC.CR01._PLD due to previous error
(AE_NOT_FOUND) (20220331/psparse-529)
platform MSFT0101:00: failed to claim resource 1: [mem
0xfed40000-0xfed40fff]
acpi MSFT0101:00: platform device creation failed: -16
lis3lv02d: unknown sensor type 0x0

Are they serious? Should they be reported or not? Is my laptop properly
working? I have no clue at all.

---

While we've been talking about bugzilla I thought it would be pertinent
to bring this up.

Best regards,
Artem