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:   Wed, 22 Nov 2017 08:52:51 +0100
From:   Takashi Iwai <tiwai@...e.de>
To:     Laura Abbott <labbott@...hat.com>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        PaX Team <pageexec@...email.hu>
Subject: Re: Regression with a91d66129fb9 ("ALSA: hda - Fix incorrect TLV callback check introduced during set_fs() removal")

On Tue, 21 Nov 2017 17:25:05 +0100,
Takashi Iwai wrote:
> 
> On Tue, 21 Nov 2017 17:14:42 +0100,
> Laura Abbott wrote:
> > 
> > Hi,
> > 
> > Fedora got a bug report (https://bugzilla.redhat.com/show_bug.cgi?id=1512853)
> > that Line Out stopped working between 4.13.9 and 4.13.10. Reverting
> > 82d745a55779 ("ALSA: hda - Fix incorrect TLV callback check introduced during set_fs() removal")
> > fixed the problem. I didn't ask the reporter to test on 4.14 since I didn't see
> > anything explicitly tagged as fixing the issue. Any ideas?
> 
> It might be that the formerly saved asound.state brought the
> inconsistency.  Try to remove the saved state (either
> /var/lib/alsa/asound.state or /etc/asound.state) after unloading the
> sound driver modules and reboot/retest.
> 
> In anyway, give alsa-info.sh output with the affected machine.
> Run the script with --no-upload option, and attach the generated
> file.

BTW, having the output of alsa-info.sh with a bug report helps
analysis and debugging quite a lot.

So it'd be appreciated if you can ask it always as the first step for
a bug report on Fedora regarding sound.  Especially when it's a
regression, the outputs on both working and non-working cases would be
nice, so that we can compare more precisely.


thanks,

Takashi

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ