stable.vger.kernel.org archive mirror
 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] SUNRPC: Remove BUG_ON call sites
Date: Wed, 6 Nov 2024 07:13:00 +0100	[thread overview]
Message-ID: <2024110646-crimson-eldest-b168@gregkh> (raw)
In-Reply-To: <ZyXOg2gepysQBic0@codewreck.org>

On Sat, Nov 02, 2024 at 04:02:27PM +0900, Dominique Martinet wrote:
> Dominique Martinet wrote on Sat, Nov 02, 2024 at 03:52:03PM +0900:
> > 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>
> 
> grmbl, missing my signed-off, sorry:
> Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>
> 
> hopefully didn't miss anything else..

Can you resend with this fixed up so we don't have to manually edit
this?

thanks,

greg k-h

      reply	other threads:[~2024-11-06  6:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-02  6:52 [PATCH 6.6] SUNRPC: Remove BUG_ON call sites Dominique Martinet
2024-11-02  7:02 ` Dominique Martinet
2024-11-06  6:13   ` 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=2024110646-crimson-eldest-b168@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;
as well as URLs for NNTP newsgroup(s).