From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [bug report] f2fs: off by one in garbage collection functions
Date: Mon, 21 Jan 2013 09:58:15 +0900 [thread overview]
Message-ID: <1358729895.8234.147.camel@kjgkr> (raw)
In-Reply-To: <20130118132949.GA5708@elgon.mountain>
[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]
Hi,
2013-01-18 (금), 16:29 +0300, Dan Carpenter:
> Hello Jaegeuk Kim,
>
> The patch 7bc0900347e0: "f2fs: add garbage collection functions" from
> Nov 2, 2012, has an off-by-one bug.
>
> 429 block_t start_bidx_of_node(unsigned int node_ofs)
> 430 {
> 431 unsigned int indirect_blks = 2 * NIDS_PER_BLOCK + 4;
> 432 unsigned int bidx;
> 433
> 434 if (node_ofs == 0)
> 435 return 0;
> 436
> 437 if (node_ofs <= 2) {
> 438 bidx = node_ofs - 1;
> 439 } else if (node_ofs <= indirect_blks) {
> 440 int dec = (node_ofs - 4) / (NIDS_PER_BLOCK + 1);
>
> If node_ofs == 3 here then (node_ofs - 4) is a very high positive
> number. We divide by 1019 and we get another still very high number but
> not so high that it is negative when cast as an int.
If the node_ofs is equal to 3, then it's a run-time bug on its caller,
gc_data_segment(), not here itself.
In gc_data_segment(),
1. check_dnode(&nofs);
2. start_bidx_of_node(nofs);
Here, it means that we don't care about indirect node pages whose node
offsets are 3, 3+1018+1, (3+1018+1)+1018+1, and so on.
(Ref. *Index Structure* in Document/filesystems/f2fs.txt)
Instead, we just check direct node pages only.
But, anyway, I'd better write comments to make it clear.
Thank you for reviewing.
--
Jaegeuk Kim
Samsung
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-01-21 0:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 13:29 Dan Carpenter
2013-01-21 0:58 ` Jaegeuk Kim [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=1358729895.8234.147.camel@kjgkr \
--to=jaegeuk.kim@samsung.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®