ACK/cmnt: [Cover Letter] Out of order reads can fetch a NULL pointer causing a kernel crash

[Kleber Souza]

On 27.04.21 14:27, Guilherme Piccoli wrote:
> On Tue, Apr 27, 2021 at 7:44 AM Kleber Souza <kleber.souza at canonical.com> wrote:
>>
>> Hi Guilherme,
>>
>> For the next submissions, could you please add to the cover letter the affected
>> kernels as well? Ideally it would also have the "[SRU]" tag as well. This makes
>> it easier to identify for which kernels the patches need to be applied.
>>
>> Otherwise the patches look good.
>>
>> Acked-by: Kleber Sacilotto de Souza <kleber.souza at canonical.com>
>>
>> Thanks
> 
> Thanks Kleber!
> 
> About the cover letter subject, for sure! I usually do that...I just
> got confused due to the situation here: this series is for all kernels
> B/F/G/H, but I've tested them on linux-aws for these series (and it is
> a priority there). How should I encode this information in the
> cover-letter subject, through tags? Suggestions are very appreciated!
> Cheers,
> 

Hey Guilherme,

Yeah, this is a special situation. We usually don't need to send the
same patches to derivatives and their main kernels at the same time.
Regarding aws being a priority, I think it was well described in the
cover letter and it would be difficult to represent this on the subject.

So what I think could be a good way to tag the kernels affected by the whole
thread would be something similar to what has been done on the third patch
of the series, for example: "[B/F/G/H:linux][B/F/G/H:linux-aws]"


Thanks,
Kleber