Skip to content

fix: ensure forward progress in __file_lookup when nr_blk = 0 #88

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
EricKim27 wants to merge 3 commits into from
Closed

fix: ensure forward progress in __file_lookup when nr_blk = 0 #88

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
12b3356
fix: ensure forward progress in __file_lookup when nr_blk = 0
EricKim27 Jun 19, 2026
9b04f7b
fixing coding style conventions
EricKim27 Jun 19, 2026
444918a
cleaning up code
EricKim27 Jun 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions inode.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -186,6 +186,14 @@ static int __file_lookup(struct inode *dir,
*fi = _fi;
return 0;
}
if(!dblock->files[_fi].nr_blk){
/*
this means the _ei and _bi we're looking for is looking at an empty block.
we have to advance nontheless, but nr_blk would just add 0 to fi, causing endless loop.
so we skip this entry by 1, just in case.
*/
_fi += 1;
}
_fi += dblock->files[_fi].nr_blk;
Comment thread
cubic-dev-ai[bot] marked this conversation as resolved.
Outdated
}
RELEASE_BUFFER_HEAD(*ret_bi_bh);
Expand Down
Loading