Skip to content
Snippets Groups Projects
Select Git revision
  • ec9436baedb689668c409cfc8b69eb9573b0d661
  • master default
  • vpu-jpeg-h264-wip
  • vpu-ficus-v2
  • wip-vpu-jpeg-v1
  • m2m-mc-v3
  • vpu-ficus-wip
  • proc-cmdline
  • v4.18-rc1
  • v4.17
  • v4.17-rc7
  • v4.17-rc6
  • v4.17-rc5
  • v4.17-rc4
  • v4.17-rc3
  • v4.17-rc2
  • v4.17-rc1
  • v4.16
  • v4.16-rc7
  • v4.16-rc6
  • v4.16-rc5
  • v4.16-rc4
  • v4.16-rc3
  • v4.16-rc2
  • v4.16-rc1
  • v4.15
  • v4.15-rc9
  • v4.15-rc8
28 results

dsa.h

user avatar
Andrew Jones authored and Palmer Dabbelt committed
Commit 78e5a339 ("cpumask: fix checking valid cpu range") has
started issuing warnings[*] when cpu indices equal to nr_cpu_ids - 1
are passed to cpumask_next* functions. seq_read_iter() and cpuinfo's
start and next seq operations implement a pattern like

  n = cpumask_next(n - 1, mask);
  show(n);
  while (1) {
      ++n;
      n = cpumask_next(n - 1, mask);
      if (n >= nr_cpu_ids)
          break;
      show(n);
  }

which will issue the warning when reading /proc/cpuinfo. Ensure no
warning is generated by validating the cpu index before calling
cpumask_next().

[*] Warnings will only appear with DEBUG_PER_CPU_MAPS enabled.

Signed-off-by: default avatarAndrew Jones <ajones@ventanamicro.com>
Reviewed-by: default avatarAnup Patel <anup@brainfault.org>
Reviewed-by: default avatarConor Dooley <conor.dooley@microchip.com>
Tested-by: default avatarConor Dooley <conor.dooley@microchip.com>
Acked-by: default avatarYury Norov <yury.norov@gmail.com>
Link: https://lore.kernel.org/r/20221014155845.1986223-2-ajones@ventanamicro.com/


Fixes: 78e5a339 ("cpumask: fix checking valid cpu range")
Cc: stable@vger.kernel.org
Signed-off-by: default avatarPalmer Dabbelt <palmer@rivosinc.com>
d14e99bf
History