linux-kernel - Re: [PATCH 1/3] Revert "ASoC: Intel: Skylake: Acquire irq after RIRB allocation"

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]

Message-ID: <20180911163636.GC10123@sirena.org.uk>
Date:   Tue, 11 Sep 2018 17:36:36 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Takashi Iwai <tiwai@...e.de>
Cc:     Yu Zhao <yuzhao@...gle.com>, alsa-devel@...a-project.org,
        Guneshwor Singh <guneshwor.o.singh@...el.com>,
        Naveen Manohar <naveen.m@...el.com>,
        Pankaj Bharadiya <pankaj.laxminarayan.bharadiya@...el.com>,
        Rakesh Ughreja <rakesh.a.ughreja@...el.com>,
        Sanyog Kale <sanyog.r.kale@...el.com>,
        Sriram Periyasamy <sriramx.periyasamy@...el.com>,
        Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
        Jie Yang <yang.jie@...ux.intel.com>,
        Jaroslav Kysela <perex@...ex.cz>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] Revert "ASoC: Intel: Skylake: Acquire irq after RIRB
 allocation"

On Tue, Sep 11, 2018 at 08:03:21AM +0200, Takashi Iwai wrote:
> Yu Zhao wrote:

> > Will fix the problems in the following patches. Also attaching the
> > crash for future reference.

> > [   16.950887] RIP: 0010:snd_hdac_bus_update_rirb+0x19b/0x4cf [snd_hda_core]
> > [   16.950889] RSP: 0000:ffff88015c807c08 EFLAGS: 00010003
> > [   16.950891] RAX: 0000000000000101 RBX: 000000000000080c RCX: 1ffff10026822185

> Please try to rip off uninteresting hex values and other stuff there.

Right:

Please think hard before including complete backtraces in upstream
reports, they are very large and contain almost no useful information
relative to their size so often obscure the relevant content in your
message. If part of the backtrace is usefully illustrative then it's
usually better to pull out the relevant sections.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)