From: Chao Yu <yuchao0@huawei.com> To: Dan Carpenter <dan.carpenter@oracle.com>, Jaegeuk Kim <jaegeuk@kernel.org> Cc: kernel-janitors@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Subject: Re: [PATCH] f2fs: signedness bug in f2fs_fname_setup_ci_filename() Date: Wed, 04 Sep 2019 11:43:07 +0000 [thread overview] Message-ID: <29accb39-1ed7-ab3f-4783-9a07836db8e3@huawei.com> (raw) In-Reply-To: <20190904100239.GC7007@mwanda> On 2019/9/4 18:02, Dan Carpenter wrote: > The error handling doesn't work because "cf_name->len" is unsigned. Dan, thanks for catching this, would you mind merging this into original patch, since it's still in the dev branch. :) Thanks, > > Fixes: fbce5d4ab3ab ("f2fs: optimize case-insensitive lookups") > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> > --- > fs/f2fs/dir.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/fs/f2fs/dir.c b/fs/f2fs/dir.c > index 9de688a4e115..c83b666f9d7e 100644 > --- a/fs/f2fs/dir.c > +++ b/fs/f2fs/dir.c > @@ -157,7 +157,7 @@ void f2fs_fname_setup_ci_filename(struct inode *dir, > cf_name->len = utf8_casefold(sbi->s_encoding, > iname, cf_name->name, > F2FS_NAME_LEN); > - if (cf_name->len <= 0) { > + if ((int)cf_name->len <= 0) { > kvfree(cf_name->name); > cf_name->name = NULL; > } >
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <yuchao0@huawei.com> To: Dan Carpenter <dan.carpenter@oracle.com>, Jaegeuk Kim <jaegeuk@kernel.org> Cc: kernel-janitors@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Subject: Re: [f2fs-dev] [PATCH] f2fs: signedness bug in f2fs_fname_setup_ci_filename() Date: Wed, 4 Sep 2019 19:43:07 +0800 [thread overview] Message-ID: <29accb39-1ed7-ab3f-4783-9a07836db8e3@huawei.com> (raw) In-Reply-To: <20190904100239.GC7007@mwanda> On 2019/9/4 18:02, Dan Carpenter wrote: > The error handling doesn't work because "cf_name->len" is unsigned. Dan, thanks for catching this, would you mind merging this into original patch, since it's still in the dev branch. :) Thanks, > > Fixes: fbce5d4ab3ab ("f2fs: optimize case-insensitive lookups") > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com> > --- > fs/f2fs/dir.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/fs/f2fs/dir.c b/fs/f2fs/dir.c > index 9de688a4e115..c83b666f9d7e 100644 > --- a/fs/f2fs/dir.c > +++ b/fs/f2fs/dir.c > @@ -157,7 +157,7 @@ void f2fs_fname_setup_ci_filename(struct inode *dir, > cf_name->len = utf8_casefold(sbi->s_encoding, > iname, cf_name->name, > F2FS_NAME_LEN); > - if (cf_name->len <= 0) { > + if ((int)cf_name->len <= 0) { > kvfree(cf_name->name); > cf_name->name = NULL; > } > _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-09-04 11:43 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-09-04 10:02 [PATCH] f2fs: signedness bug in f2fs_fname_setup_ci_filename() Dan Carpenter 2019-09-04 10:02 ` [f2fs-dev] " Dan Carpenter 2019-09-04 11:43 ` Chao Yu [this message] 2019-09-04 11:43 ` Chao Yu 2019-09-04 12:44 ` Dan Carpenter 2019-09-04 12:44 ` [f2fs-dev] " Dan Carpenter
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=29accb39-1ed7-ab3f-4783-9a07836db8e3@huawei.com \ --to=yuchao0@huawei.com \ --cc=dan.carpenter@oracle.com \ --cc=jaegeuk@kernel.org \ --cc=kernel-janitors@vger.kernel.org \ --cc=linux-f2fs-devel@lists.sourceforge.net \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.