From: Li zeming <zeming@nfschina.com>
To: neilb@suse.de
Cc: bvanassche@acm.org, jlayton@kernel.org,
linux-kernel@vger.kernel.org, reiserfs-devel@vger.kernel.org,
song@kernel.org, willy@infradead.org
Subject: Re: [PATCH] reiserfs: journal: Increase jl pointer check
Date: Wed, 26 Oct 2022 09:47:26 +0800 [thread overview]
Message-ID: <20221026014727.3020-1-zeming@nfschina.com> (raw)
In-Reply-To: <166673341340.7585.173987927705263434@noble.neil.brown.name>
I'm sorry, I think __GFP_NOFAIL should be like this:
The __GFP_NOFAIL flag will cause memory to be allocated an infinite
number of times until the allocation is successful, but it is best to
use it only for very necessary code, and try not to use it.
I'm not sure alloc_journal_list function is a very important function
here. If it is, this patch ignores it and does not consider it anymore
__GFP_NOFAIL allocatiIon problem.
next prev parent reply other threads:[~2022-10-26 1:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 8:47 Li zeming
2022-10-25 21:30 ` NeilBrown
2022-10-26 1:47 ` Li zeming [this message]
2022-10-26 3:05 ` NeilBrown
2022-10-26 3:55 ` Li zeming
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=20221026014727.3020-1-zeming@nfschina.com \
--to=zeming@nfschina.com \
--cc=bvanassche@acm.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=reiserfs-devel@vger.kernel.org \
--cc=song@kernel.org \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®