Message ID | 1428030822-51540-1-git-send-email-shengyong1@huawei.com |
---|---|
State | Accepted |
Headers | show |
On Fri, 2015-04-03 at 03:13 +0000, Sheng Yong wrote: > The INUM_WATERMARK is a unsigned 32bit value, `%d' prints it as negatave: > [ 103.682255] UBIFS warning (ubi0:0 pid 691): ubifs_new_inode: running out of inode numbers (current 122763, max -256) > > Fix it as: > [ 154.422940] UBIFS warning (ubi0:0 pid 688): ubifs_new_inode: running out of inode numbers (current 122765, max 4294967040) > > Signed-off-by: Sheng Yong <shengyong1@huawei.com> Picked this one. It fixes one of your previous patches, and it is trivial, so I put it straight to linux-next.
diff --git a/fs/ubifs/dir.c b/fs/ubifs/dir.c index 90fe60c..02d1ee7 100644 --- a/fs/ubifs/dir.c +++ b/fs/ubifs/dir.c @@ -151,7 +151,7 @@ struct inode *ubifs_new_inode(struct ubifs_info *c, const struct inode *dir, iput(inode); return ERR_PTR(-EINVAL); } - ubifs_warn(c, "running out of inode numbers (current %lu, max %d)", + ubifs_warn(c, "running out of inode numbers (current %lu, max %u)", (unsigned long)c->highest_inum, INUM_WATERMARK); }
The INUM_WATERMARK is a unsigned 32bit value, `%d' prints it as negatave: [ 103.682255] UBIFS warning (ubi0:0 pid 691): ubifs_new_inode: running out of inode numbers (current 122763, max -256) Fix it as: [ 154.422940] UBIFS warning (ubi0:0 pid 688): ubifs_new_inode: running out of inode numbers (current 122765, max 4294967040) Signed-off-by: Sheng Yong <shengyong1@huawei.com> --- fs/ubifs/dir.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)