From: Guillaume Nault <gnault@redhat.com>
To: Trond Myklebust <trondmy@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>,
linux-nfs@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Benjamin Coddington <bcodding@redhat.com>,
netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH v2] sunrpc: Use GFP_NOFS to prevent use of current->task_frag.
Date: Tue, 25 Oct 2022 13:15:25 +0200 [thread overview]
Message-ID: <20221025111525.GA4415@localhost.localdomain> (raw)
In-Reply-To: <20221013121834.GA3353@localhost.localdomain>
On Thu, Oct 13, 2022 at 02:18:37PM +0200, Guillaume Nault wrote:
> Still, that looks like net-next material to me. Reverting sunrpc to use
> GFP_NOFS looks better for an immediate bug fix.
Could we please move forward with this patch? This bug really needs to be
fixed. So please let's either revert to GFP_NOFS or actively work on a
different solution.
next prev parent reply other threads:[~2022-10-25 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <de6d99321d1dcaa2ad456b92b3680aa77c07a747.1665401788.git.gnault@redhat.com>
[not found] ` <Y0QyYV1Wyo4vof70@infradead.org>
[not found] ` <20221010165650.GA3456@ibm-p9z-18-fsp.mgmt.pnr.lab.eng.rdu2.redhat.com>
[not found] ` <Y0UKq62ByUGNQpuY@infradead.org>
[not found] ` <20221011150057.GB3606@localhost.localdomain>
[not found] ` <a0bf0d49a7a69d20cfe007d66586a2649557a30b.camel@kernel.org>
[not found] ` <20221011211433.GA13385@ibm-p9z-18-fsp.mgmt.pnr.lab.eng.rdu2.redhat.com>
2022-10-13 12:18 ` [PATCH v2] sunrpc: Use GFP_NOFS to prevent use of current->task_frag Guillaume Nault
2022-10-25 11:15 ` Guillaume Nault [this message]
2022-12-07 11:47 ` Benjamin Coddington
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=20221025111525.GA4415@localhost.localdomain \
--to=gnault@redhat.com \
--cc=anna@kernel.org \
--cc=bcodding@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=edumazet@google.com \
--cc=hch@infradead.org \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=trond.myklebust@hammerspace.com \
--cc=trondmy@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).