stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: stable@vger.kernel.org,
	Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
	Kees Cook <keescook@chromium.org>, SeongJae Park <sj@kernel.org>,
	Seth Jenkins <sethjenkins@google.com>,
	Jann Horn <jannh@google.com>,
	"Eric W . Biederman" <ebiederm@xmission.com>,
	linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4.14 v2 00/15] Backport oops_limit to 4.14
Date: Fri, 3 Feb 2023 08:57:55 +0100	[thread overview]
Message-ID: <Y9y+g66x++h4kEXy@kroah.com> (raw)
In-Reply-To: <20230203003354.85691-1-ebiggers@kernel.org>

On Thu, Feb 02, 2023 at 04:33:39PM -0800, Eric Biggers wrote:
> This series backports the patchset
> "exit: Put an upper limit on how often we can oops"
> (https://lore.kernel.org/linux-mm/20221117233838.give.484-kees@kernel.org/T/#u)
> to 4.14, as recommended at
> https://googleprojectzero.blogspot.com/2023/01/exploiting-null-dereferences-in-linux.html
> 
> Changed in v2:
>    - Fixed a build error in mm/kasan/report.c by dropping the patch "mm:
>      kasan: do not panic if both panic_on_warn and kasan_multishot set".

Both v2 series now queued up, let's see if they build...

thanks,

greg k-h

      parent reply	other threads:[~2023-02-03  7:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03  0:33 [PATCH 4.14 v2 00/15] Backport oops_limit to 4.14 Eric Biggers
2023-02-03  0:33 ` [PATCH 4.14 v2 01/15] sysctl: add a new register_sysctl_init() interface Eric Biggers
2023-02-03  0:33 ` [PATCH 4.14 v2 02/15] panic: unset panic_on_warn inside panic() Eric Biggers
2023-02-03  0:33 ` [PATCH 4.14 v2 03/15] exit: Add and use make_task_dead Eric Biggers
2023-02-03  0:33 ` [PATCH 4.14 v2 04/15] objtool: Add a missing comma to avoid string concatenation Eric Biggers
2023-02-03  0:33 ` [PATCH 4.14 v2 05/15] hexagon: Fix function name in die() Eric Biggers
2023-02-03  0:33 ` [PATCH 4.14 v2 06/15] h8300: Fix build errors from do_exit() to make_task_dead() transition Eric Biggers
2023-02-03  0:33 ` [PATCH 4.14 v2 07/15] ia64: make IA64_MCA_RECOVERY bool instead of tristate Eric Biggers
2023-02-03  0:33 ` [PATCH 4.14 v2 08/15] exit: Put an upper limit on how often we can oops Eric Biggers
2023-02-03  0:33 ` [PATCH 4.14 v2 09/15] exit: Expose "oops_count" to sysfs Eric Biggers
2023-02-03  0:33 ` [PATCH 4.14 v2 10/15] exit: Allow oops_limit to be disabled Eric Biggers
2023-02-03  0:33 ` [PATCH 4.14 v2 11/15] panic: Consolidate open-coded panic_on_warn checks Eric Biggers
2023-02-03  0:33 ` [PATCH 4.14 v2 12/15] panic: Introduce warn_limit Eric Biggers
2023-02-03  0:33 ` [PATCH 4.14 v2 13/15] panic: Expose "warn_count" to sysfs Eric Biggers
2023-02-03  0:33 ` [PATCH 4.14 v2 14/15] docs: Fix path paste-o for /sys/kernel/warn_count Eric Biggers
2023-02-03  0:33 ` [PATCH 4.14 v2 15/15] exit: Use READ_ONCE() for all oops/warn limit reads Eric Biggers
2023-02-03  7:57 ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y9y+g66x++h4kEXy@kroah.com \
    --to=greg@kroah.com \
    --cc=ebiederm@xmission.com \
    --cc=ebiggers@kernel.org \
    --cc=harshit.m.mogalapalli@oracle.com \
    --cc=jannh@google.com \
    --cc=keescook@chromium.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sethjenkins@google.com \
    --cc=sj@kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).