From: Christoph Hellwig <hch@infradead.org>
To: Chaitanya Kulkarni <ckulkarnilinux@gmail.com>
Cc: kbusch@kernel.org, hch@lst.de, hare@suse.de, sagi@grimberg.me,
axboe@kernel.dk, dlemoal@kernel.org, wagi@kernel.org,
mpatocka@redhat.com, yukuai3@huawei.com, xni@redhat.com,
linan122@huawei.com, bmarzins@redhat.com,
john.g.garry@oracle.com, edumazet@google.com,
ncardwell@google.com, kuniyu@google.com, davem@davemloft.net,
dsahern@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org
Subject: Re: [RFC blktests fix PATCH] tcp: use GFP_ATOMIC in tcp_disconnect
Date: Mon, 24 Nov 2025 22:27:41 -0800 [thread overview]
Message-ID: <aSVMXYCiEGpETx-X@infradead.org> (raw)
In-Reply-To: <20251125061142.18094-1-ckulkarnilinux@gmail.com>
I don't think GFP_ATOMIC is right here, you want GFP_NOIO.
And just use the scope API so that you don't have to pass a gfp_t
several layers down.
next prev parent reply other threads:[~2025-11-25 6:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 6:11 [RFC blktests fix PATCH] tcp: use GFP_ATOMIC in tcp_disconnect Chaitanya Kulkarni
2025-11-25 6:27 ` Christoph Hellwig [this message]
2025-11-25 7:28 ` Chaitanya Kulkarni
2025-11-25 11:08 ` hch
2025-11-25 11:13 ` Nilay Shroff
2025-11-25 11:21 ` hch
2025-11-25 11:28 ` Nilay Shroff
2025-11-25 11:30 ` Christoph Hellwig
2025-11-25 11:54 ` Nilay Shroff
2025-11-25 12:33 ` Hannes Reinecke
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=aSVMXYCiEGpETx-X@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=bmarzins@redhat.com \
--cc=ckulkarnilinux@gmail.com \
--cc=davem@davemloft.net \
--cc=dlemoal@kernel.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=horms@kernel.org \
--cc=john.g.garry@oracle.com \
--cc=kbusch@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linan122@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mpatocka@redhat.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sagi@grimberg.me \
--cc=wagi@kernel.org \
--cc=xni@redhat.com \
--cc=yukuai3@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.