Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: stable@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>,
	Christian Brauner <brauner@kernel.org>, NeilBrown <neilb@suse.de>,
	Jeff Layton <jlayton@kernel.org>
Subject: Re: [PATCH 6.6 v2] SUNRPC: Remove BUG_ON call sites
Date: Wed, 6 Nov 2024 09:01:06 +0100	[thread overview]
Message-ID: <2024110659-falcon-poser-545d@gregkh> (raw)
In-Reply-To: <20241106075457.201502-3-asmadeus@codewreck.org>

On Wed, Nov 06, 2024 at 04:54:59PM +0900, Dominique Martinet wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
> 
> [ Upstream commit 789ce196a31dd13276076762204bee87df893e53 ]
> 
> There is no need to take down the whole system for these assertions.
> 
> I'd rather not attempt a heroic save here, as some bug has occurred
> that has left the transport data structures in an unknown state.
> Just warn and then leak the left-over resources.
> 
> Acked-by: Christian Brauner <brauner@kernel.org>
> Reviewed-by: NeilBrown <neilb@suse.de>
> Reviewed-by: Jeff Layton <jlayton@kernel.org>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>
> ---
> v2: resend with signoff properly set as requested
> v1: https://lkml.kernel.org/r/20241102065203.13291-1-asmadeus@codewreck.org

Thanks, now queued up.

greg k-h

      reply	other threads:[~2024-11-06  8:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06  7:54 [PATCH 6.6 v2] SUNRPC: Remove BUG_ON call sites Dominique Martinet
2024-11-06  8:01 ` 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=2024110659-falcon-poser-545d@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=asmadeus@codewreck.org \
    --cc=brauner@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=neilb@suse.de \
    --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