linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: Issue with RT patchset refresh on top of 4.9.175 as rebase for stretch due to 59c39840f5abf4a71e1810a8da71aaccd6c17d26
       [not found] <20190511120422.GA1212@eldamar.local>
@ 2019-05-11 13:47 ` Sebastian Andrzej Siewior
  0 siblings, 0 replies; only message in thread
From: Sebastian Andrzej Siewior @ 2019-05-11 13:47 UTC (permalink / raw)
  To: Salvatore Bonaccorso; +Cc: linux-rt-users, Steven Rostedt

[-- Attachment #1: Type: text/plain, Size: 1883 bytes --]

On 2019-05-11 14:04:22 [+0200], Salvatore Bonaccorso wrote:
> Hi Sebastian,
Hi Salvatore,

> I wonder if you can help me out on the following issue in case there
> will be no new RT patchsets for the 4.9 series soonish. I'm working on
> importing new 4.9 upstream version to be released in future stretch
> point releases.
> 
> https://salsa.debian.org/kernel-team/linux/merge_requests/141
> 
> is my current work in progress with an import of 4.9.175 for stretch.
> Though the backport of 59c39840f5ab ("genirq: Prevent use-after-free
> and work list corruption") ro 4.9.175 will cause issues for the RT
> patchset:
> /home/build/linux-4.9.175/debian/build/source_rt/kernel/irq/manage.c: In function 'irq_set_affinity_notifier':
> /home/build/linux-4.9.175/debian/build/source_rt/kernel/irq/manage.c:375:31: error: 'struct irq_affinity_notify' has no member named 'work'; did you mean 'swork'?
>    cancel_work_sync(&old_notify->work);
> Now I could have mail the kernel development mailinglist or rt-users
> mailinglist, the reason I did contact you directly is that I have not
> found if the issue was already raised.

Nope, I'm not aware of it.

> Will there be new RT patchsets soon as the various stable branches all
> contained that commit (v5.1.1~19, v5.0.15~23, v4.19.42~17,
> v4.14.118~13 and v4.9.175~10), or should I try to work on refreshing
> the patchsets on my own, ideally with your help here :)

Please find attached an archive with three patches. That are basically
backports from the v5.0-RT tree. The kswork does not offer a "flush" which
would be required. I feel more comfortable to switch to the kthread
based infrastructure (which is used in the v5.0-RT tree) than adding the
required flush bits (and testing and so on) to kwork.

> Thanks for your time reading so far!
> 
> Regards,
> Salvatore

Sebastian

[-- Attachment #2: kwork.tar.xz --]
[-- Type: application/x-xz, Size: 3700 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2019-05-11 13:47 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20190511120422.GA1212@eldamar.local>
2019-05-11 13:47 ` Issue with RT patchset refresh on top of 4.9.175 as rebase for stretch due to 59c39840f5abf4a71e1810a8da71aaccd6c17d26 Sebastian Andrzej Siewior

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).