MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date:   Wed, 10 Nov 2021 17:30:48 +0100
From:   Michael Walle <michael@walle.cc>
To:     Mark Brown <broonie@kernel.org>
Cc:     linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
        =?UTF-8?Q?Uw?= =?UTF-8?Q?e_Kleine-K=C3=B6nig?= 
        <u.kleine-koenig@pengutronix.de>,
        Vladimir Oltean <olteanv@gmail.com>
Subject: Re: [RFC PATCH] spi: fix use-after-free of the add_lock mutex
In-Reply-To: <YYvy79HfTvy8hC5/@sirena.org.uk>
References: <20211110160836.3304104-1-michael@walle.cc>
 <YYvy79HfTvy8hC5/@sirena.org.uk>
User-Agent: Roundcube Webmail/1.4.11
Message-ID: <116159a7cf1e7cb3817aa31931b81d91@walle.cc>
Precedence: bulk

Am 2021-11-10 17:27, schrieb Mark Brown:
>> For reference, the kernel oops is:
>> [   20.242505] Unable to handle kernel paging request at virtual 
>> address 0042a2203dc65260
>> [   20.250468] Mem abort info:
>> [   20.253270]   ESR = 0x96000044
> 
> 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 (it often is
> for search engines if nothing else) then it's usually better to pull 
> out
> the relevant sections.

It was in the comments section of the patch, for exactly this purpose.
That's how you're doing it, no?

-michael