linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@dilger.ca>
To: liu.song11@zte.com.cn
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>,
	fishland@aliyun.com, wang.yi59@zte.com.cn,
	Ext4 Developers List <linux-ext4@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ext4: direct return when jinode allocate failed
Date: Wed, 17 Oct 2018 17:28:55 -0600	[thread overview]
Message-ID: <EA9B5AA4-DA21-4B1D-9E89-8C9F16EB8986@dilger.ca> (raw)
In-Reply-To: <201810171026448096961@zte.com.cn>

[-- Attachment #1: Type: text/plain, Size: 2417 bytes --]


> On Oct 16, 2018, at 8:26 PM, liu.song11@zte.com.cn wrote:
> 
>> On Tue, Oct 16, 2018 at 10:55:26PM +0800, fishland wrote:
>>> The jinode does not need protected by *i_lock*, we can return
>>> directly if memory allocation fails.
>>> 
>> 
>> I don't see anything wrong with this patch, but at the same time, I'm
>> not sure I see the benefit, either.  Checking for the allocation
>> failure is cheap, and moving it out spinlock doesn't buy much; not to
>> mention that the allocation failure is going to be highly uncommon.
>> 
>> What inspired this commit?
>> 
>> - Ted
> 
> Hi, Ted
> I found this during code reading. All code logic is very smooth, when
> reading here, need to spin_unlock before "return -ENOMEM", which I
> feel this could more close to the allocate. I refer to other processing
> logic for this situation in "inode.c", found that they all return immediately
> after memory application failed. I agree with you that the benefit of this
> patch is almost none, however it can slightly improve the code in rare case.

Looking at the patch there are two effects that it has:
- optimize a very rare case where there is an allocation failure before locking
- return an unnecessary error if "ei->jinode" is allocated before locking

I don't think it is worthwhile to optimize this case, since allocation failures
will have a serious impact on the application, and I'd rather avoid the rare
case where we don't return an unnecessary error than make the error case faster.

Cheers, Andreas

> 
>>> Signed-off-by: Liu Song <liu.song11@zte.com.cn>
>>> Reviewed-by: Wang Yi <wang.yi59@zte.com.cn>
>>> ---
>>> fs/ext4/inode.c | 7 +++----
>>> 1 file changed, 3 insertions(+), 4 deletions(-)
>>> 
>>> diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
>>> index d767e993591d..67ba6f062de5 100644
>>> --- a/fs/ext4/inode.c
>>> +++ b/fs/ext4/inode.c
>>> @@ -4384,12 +4384,11 @@ int ext4_inode_attach_jinode(struct inode *inode)
>>>         return 0;
>>> 
>>>  	jinode = jbd2_alloc_inode(GFP_KERNEL);
>>> +	if (!jinode)
>>> +	return -ENOMEM;
>>> +
>>>  	spin_lock(&inode->i_lock);
>>>  	if (!ei->jinode) {
>>> -		if (!jinode) {
>>> -			spin_unlock(&inode->i_lock);
>>> -			return -ENOMEM;
>>> -		}
>>>  		ei->jinode = jinode;
>>>  		jbd2_journal_init_jbd_inode(ei->jinode, inode);
>>>  		jinode = NULL;
>>> --
>>> 2.17.1


Cheers, Andreas






[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 873 bytes --]

       reply	other threads:[~2018-10-17 23:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181016145526.3288-1-fishland@aliyun.com,20181016190840.GF24131@thunk.org>
     [not found] ` <201810171026448096961@zte.com.cn>
2018-10-17 23:28   ` Andreas Dilger [this message]
2018-10-18  2:23     ` [PATCH] ext4: direct return when jinode allocate failed Theodore Y. Ts'o
     [not found] <20181016145526.3288-1-fishland@aliyun.com>
2018-10-16 19:08 ` Theodore Y. Ts'o

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=EA9B5AA4-DA21-4B1D-9E89-8C9F16EB8986@dilger.ca \
    --to=adilger@dilger.ca \
    --cc=fishland@aliyun.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liu.song11@zte.com.cn \
    --cc=tytso@mit.edu \
    --cc=wang.yi59@zte.com.cn \
    /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).