On Sat, Nov 23, 2024 at 12:35 PM Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > > On Fri, Nov 22, 2024 at 09:48:11AM -0800, Suren Baghdasaryan wrote: > > On Fri, Nov 22, 2024 at 7:04 AM Suren Baghdasaryan <surenb@xxxxxxxxxx> wrote: > > > > > > On Fri, Nov 22, 2024 at 3:07 AM Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > > > > > > > > On Thu, Nov 21, 2024 at 07:59:20PM -0800, Andrii Nakryiko wrote: > > > > > > > > > Andrii Nakryiko (2): > > > > > uprobes: simplify find_active_uprobe_rcu() VMA checks > > > > > uprobes: add speculative lockless VMA-to-inode-to-uprobe resolution > > > > > > > > Thanks, assuming Suren is okay with me carrying his patches through tip, > > > > I'll make this land in tip/perf/core after -rc1. > > > > > > No objections from me. Thanks! > > > > I just fixed a build issue in one of my patches for an odd config, so > > please use the latest version of the patchset from here: > > https://lore.kernel.org/all/20241122174416.1367052-1-surenb@xxxxxxxxxx/ > > updated, thanks! Hi Andrew, I just noticed that patches from an old version of my patchset are present in mm-unstable, more specifically these two: fb23aacd2a14 "mm: convert mm_lock_seq to a proper seqcount" 549aeb99ccf1 "mm: introduce mmap_lock_speculation_{begin|end}" Peter will be merging the latest version into tip/perf/core, so this will cause a conflict at some point. It should be easy to update them in mm-unstable to the latest version [1]. I was able to revert the old ones and apply the new ones without any merge conflict. If possible, please update them instead of dropping them from mm-unstable. Some patches I'm preparing to post have dependencies on this patchset. Thanks, Suren. [1] https://lore.kernel.org/all/20241122174416.1367052-1-surenb@xxxxxxxxxx/
