Re: [RFC PATCH V2 1/1] rasdaemon: Fix poll() on per_cpu trace_pipe_raw blocks indefinitely

[Linux regression tracking (Thorsten Leemhuis)]

On 16.02.23 14:40, Shiju Jose wrote:
> Hello,
> 
>> -----Original Message-----
>> From: Linux regression tracking (Thorsten Leemhuis)
>> <regressions@xxxxxxxxxxxxx>
>> Sent: 16 February 2023 11:48
>> To: rostedt@xxxxxxxxxxx
>> Cc: mhiramat@xxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; linux-trace-
>> kernel@xxxxxxxxxxxxxxx; tanxiaofei <tanxiaofei@xxxxxxxxxx>; Jonathan
>> Cameron <jonathan.cameron@xxxxxxxxxx>; Linuxarm
>> <linuxarm@xxxxxxxxxx>; Linux kernel regressions list
>> <regressions@xxxxxxxxxxxxxxx>; Shiju Jose <shiju.jose@xxxxxxxxxx>;
>> mchehab@xxxxxxxxxx; linux-edac@xxxxxxxxxxxxxxx
>> Subject: Re: [RFC PATCH V2 1/1] rasdaemon: Fix poll() on per_cpu
>> trace_pipe_raw blocks indefinitely
>>
>> Hi, this is your Linux kernel regression tracker.
> 
> Kernel fix patch for this issue is already in the mainline. Please see the commit
> 3e46d910d8acf94e5360126593b68bf4fee4c4a1
> ("tracing: Fix poll() and select() do not work on per_cpu trace_pipe and trace_pipe_raw")

Great, thx for letting me know.

>> On 04.02.23 20:33, shiju.jose@xxxxxxxxxx wrote:
>>> From: Shiju Jose <shiju.jose@xxxxxxxxxx>
>>>
>>> The error events are not received in the rasdaemon since kernel 6.1-rc6.
>>> This issue is firstly detected and reported, when testing the CXL
>>> error events in the rasdaemon.
>>
>> Thanks for working on this. This submission looks stalled, unless I missed
>> something. This is unfortunate, as this afaics is fixing a regression (caused by a
>> commit from Steven). Hence it would be good to get this fixed rather sooner
>> than later. Or is the RFC in the subject the reason why there was no progress? Is
>> it maybe time to remove it?
> 
> I made the pull request for this rasdaemon  patch here,
>  https://github.com/mchehab/rasdaemon/pull/86

Ha, stupid me, I didn't even notice this thread was about a rasdaemon
change (I landed here as the patch description liked to the tracked
regression report). Apologies for mixing this up; I deal with a lot of
regression reports and try to avoid mistakes like this, but they
nevertheless happen. :-/

Ciao, Thorsten