Linux kernel regression status

Latest five known activities:

• 388a1fb7da6a, the fix specified through '#regzbot fix:' earlier landed in next
  , by Peter Zijlstra
• [tip: perf/core] perf: Fix the nr_addr_filters fix
  , by tip-bot2 for Peter Zijlstra; contains a simple patch
• Re: REGRESSION linux-next since Nov 16th, perf tool broken (at least on s390)
  , by Thomas Richter
• Re: REGRESSION linux-next since Nov 16th, perf tool broken (at least on s390)
  , by Greg KH
• Re: REGRESSION linux-next since Nov 16th, perf tool broken (at least on s390)
  , by Thomas Richter

Regzbot command history:

• fix: perf: Fix the nr_addr_filters fix
  , by Linux regression tracking #update (Thorsten Leemhuis)
• fixed: 'fix' commit '388a1fb7da6a' now in 'next'
  , by Peter Zijlstra
• fix: perf: Fix the nr_addr_filters fix
  , by Linux regression tracking #update (Thorsten Leemhuis)
• note: '388a1fb7da6a' in 'next' contains a 'Fixes:' tag for the culprit of this regression
  , by Peter Zijlstra
• title: event syntax error due to narrow startup race fix
  , by Bagas Sanjaya
• introduced: 652ffc2104ec1f ^
  , by Bagas Sanjaya

All known activities:

• Re: Bug report connect to VM with Vagrant
  , by Bagas Sanjaya
• Re: Bug report connect to VM with Vagrant
  , by Eric Dumazet
• Bug report connect to VM with Vagrant
  , by Shachar Kagan

Regzbot command history:

• title: starting Vagrant VM fails due to not aborting SYN_SENT
  , by Bagas Sanjaya
• introduced: 0a8de364ff7a14 ^
  , by Bagas Sanjaya

When fixing, add this to the commit message to make regzbot notice patch postings and commits to resolve the issue:

• Fixes: 0a8de364ff7a ("tcp: no longer abort SYN_SENT when receiving some ICMP")
• Reported-by: Shachar Kagan <skagan@nvidia.com>
• Link: https://lore.kernel.org/r/MN2PR12MB44863139E562A59329E89DBEB982A@MN2PR12MB4486.namprd12.prod.outlook.com/