linux-kernel - Re: Please revert 400362f1d8dcfda3562e80e88cfc2a92cffaf9bf

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: <s5h4n0wod6w.wl%tiwai@suse.de>
Date:	Sun, 11 May 2014 11:51:51 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Fubo Chen <fubo.chen@...il.com>
Cc:	Niccolò Belli <darkbasic@...uxsystems.it>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: Please revert 400362f1d8dcfda3562e80e88cfc2a92cffaf9bf

At Sun, 11 May 2014 10:49:37 +0200,
Fubo Chen wrote:
> 
> (adding Takashi Iwai)
> 
> On Thu, May 8, 2014 at 4:06 PM, Niccolò Belli <darkbasic@...uxsystems.it> wrote:
> > Hi,
> > Sorry for posting on linux-kernel but from my experience nobody ever looks
> > at the kernel bug tracker and I would like to get it fixed before 3.15 gets
> > released.
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=75671
> >
> > It's funny to read "Still no boot quirks are called, *so it might not work
> > well on some devices*" in the commit description:
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=400362f1d8dcfda3562e80e88cfc2a92cffaf9bf
> > Why does code known to be broken hit the Linus tree? Every new kernel
> > release there is something broken to bisect, it doesn't matter if you wait
> > for the stable release or not. That's frustrating for an end user.

The bug was already fixed recently in the latest Linus tree or sound
git tree.

The sentence was misread: "it might not work" just means that it's not
tested by these specific devices.  It doesn't mean that it's known to
be broken for these devices at all.  They should still work as is via
reset_resume invocation.


Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/