Message ID | 20250108090457.512198-1-bigeasy@linutronix.de (mailing list archive) |
---|---|
Headers | show |
Series | module: Use RCU instead of RCU-sched. | expand |
On 1/8/25 10:04, Sebastian Andrzej Siewior wrote: > This is an updated version of the initial post after PeterZ made me > aware that there are users outside of the module directory. > The goal is replace the mix auf rcu_read_lock(), rcu_read_lock_sched() > and preempt_disable() with just rcu_read_lock(). Thanks for this cleanup. I've queued the fix in patch #1 on modules-fixes. For the rest, I plan to give folks more time to look at the changes as this affects a number of subsystems. If there are no other concerns, I'd then add the series on modules-next.
On 2025-01-13 12:09:27 [+0100], Petr Pavlu wrote: > Thanks for this cleanup. I've queued the fix in patch #1 on > modules-fixes. For the rest, I plan to give folks more time to look at > the changes as this affects a number of subsystems. If there are no > other concerns, I'd then add the series on modules-next. Good, thanks for the update. Sebastian
On 2025-01-13 12:09:27 [+0100], Petr Pavlu wrote: > Thanks for this cleanup. I've queued the fix in patch #1 on > modules-fixes. For the rest, I plan to give folks more time to look at > the changes as this affects a number of subsystems. If there are no > other concerns, I'd then add the series on modules-next. #26 (kprobes) clashes with the changes that have been merged upstream. Do you want me to resend the whole series or just #26? The other patches apply cleanly so far. Sebastian
On 1/24/25 18:49, Sebastian Andrzej Siewior wrote: > On 2025-01-13 12:09:27 [+0100], Petr Pavlu wrote: >> Thanks for this cleanup. I've queued the fix in patch #1 on >> modules-fixes. For the rest, I plan to give folks more time to look at >> the changes as this affects a number of subsystems. If there are no >> other concerns, I'd then add the series on modules-next. > > #26 (kprobes) clashes with the changes that have been merged upstream. > Do you want me to resend the whole series or just #26? The other patches > apply cleanly so far. I think sending only the updated patch #26 should be sufficient in this case, it's only a small adjustment. Please preferably post it as a reply to the email with that specific patch.
On 2025-01-27 13:22:17 [+0100], Petr Pavlu wrote: > On 1/24/25 18:49, Sebastian Andrzej Siewior wrote: > > On 2025-01-13 12:09:27 [+0100], Petr Pavlu wrote: > >> Thanks for this cleanup. I've queued the fix in patch #1 on > >> modules-fixes. For the rest, I plan to give folks more time to look at > >> the changes as this affects a number of subsystems. If there are no > >> other concerns, I'd then add the series on modules-next. > > > > #26 (kprobes) clashes with the changes that have been merged upstream. > > Do you want me to resend the whole series or just #26? The other patches > > apply cleanly so far. > > I think sending only the updated patch #26 should be sufficient in this > case, it's only a small adjustment. Please preferably post it as a reply > to the email with that specific patch. I just sent two updates: [PATCH v3.5 25/28] bpf: Use RCU in all users of __module_text_address(). [PATCH v3.5 26/28] kprobes: Use RCU in all users of __module_text_address(). Sebastian
On 1/29/25 09:52, Sebastian Andrzej Siewior wrote: > On 2025-01-27 13:22:17 [+0100], Petr Pavlu wrote: >> On 1/24/25 18:49, Sebastian Andrzej Siewior wrote: >>> On 2025-01-13 12:09:27 [+0100], Petr Pavlu wrote: >>>> Thanks for this cleanup. I've queued the fix in patch #1 on >>>> modules-fixes. For the rest, I plan to give folks more time to look at >>>> the changes as this affects a number of subsystems. If there are no >>>> other concerns, I'd then add the series on modules-next. >>> >>> #26 (kprobes) clashes with the changes that have been merged upstream. >>> Do you want me to resend the whole series or just #26? The other patches >>> apply cleanly so far. >> >> I think sending only the updated patch #26 should be sufficient in this >> case, it's only a small adjustment. Please preferably post it as a reply >> to the email with that specific patch. > > I just sent two updates: > > [PATCH v3.5 25/28] bpf: Use RCU in all users of __module_text_address(). > [PATCH v3.5 26/28] kprobes: Use RCU in all users of __module_text_address(). I've now queued the series and its two updated patches #25 and #26 on modules-next (for 6.15-rc1).