Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Chengguang Xu <cgxu519@mykernel.net>
To: "Jan Kara" <jack@suse.cz>
Cc: "jack" <jack@suse.com>, "linux-ext4" <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext2: adjust block num when retry allocation
Date: Tue, 22 Oct 2019 13:36:18 +0800	[thread overview]
Message-ID: <16df1f74b07.d3ade7d625647.885482535351431524@mykernel.net> (raw)
In-Reply-To: <20191021091800.GC17810@quack2.suse.cz>

 ---- 在 星期一, 2019-10-21 17:18:00 Jan Kara <jack@suse.cz> 撰写 ----
 > On Mon 21-10-19 07:23:26, Chengguang Xu wrote:
 > > Set block num to original *count in a case
 > > of retrying allocation in case num < *count
 > > 
 > > Signed-off-by: Chengguang Xu <cgxu519@mykernel.net>
 > > ---
 > > Hi Jan,
 > > 
 > > This patch is only compile-tested, I'm not sure if this
 > > kind of unexpected condition which causes reallocation
 > > will actually happen but baesd on the code the fix seems
 > > correct and better.
 > 
 > Yeah, you are right that we should reset 'num' back to *count. Although the
 > practial effect of this is minimal - we take this code path only when the
 > filesystem is corrupted. But still... Patch applied. Thanks!
 
Thanks for your review. I found another relevant bug in ext2_try_to_allocate()
today, I'll fix it up and  also plan to do some code cleanups for the allocation logic.
Do you prefer two separate patches for bugfix and cleanup or just put all in a patch series?

Thanks,
Chengguang







      reply	other threads:[~2019-10-22  5:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-20 23:23 [PATCH] ext2: adjust block num when retry allocation Chengguang Xu
2019-10-21  9:18 ` Jan Kara
2019-10-22  5:36   ` Chengguang Xu [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=16df1f74b07.d3ade7d625647.885482535351431524@mykernel.net \
    --to=cgxu519@mykernel.net \
    --cc=jack@suse.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@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