linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: "Xu, Wen" <wen.xu@gatech.edu>
To: Chao Yu <chao@kernel.org>
Cc: "linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: Bug report: some new bugs found by fuzzing
Date: Sun, 8 Jul 2018 02:43:34 +0000	[thread overview]
Message-ID: <14604831-EB4B-421F-B5E4-BB159611D850@gatech.edu> (raw)
In-Reply-To: <ed7af144-d43e-386b-5f0f-b9899023afe5@kernel.org>

It is already fixed by the latest commit in your git tree?

Thanks,
Wen

> On Jul 7, 2018, at 12:32 PM, Chao Yu <chao@kernel.org> wrote:
> 
> On 2018/7/7 23:48, Xu, Wen wrote:
>> Sure I will do it. So you are still willing to fix the issues even it may be affected by CHECK_FS config?
> 
> Yes, let me figure out the problem.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/commit/?h=f2fs-dev&id=ccf5e1525e92010dd2cb8ff5a820283f9bff5c78
> 
> Above commit seems breaking normal case, let me update it.
> 
> Thanks,
> 
>> 
>> Thanks
>> -Wen
>> 
>>> On Jul 6, 2018, at 12:22 PM, Chao Yu <chao@kernel.org> wrote:
>>> 
>>> Hi Wen,
>>> 
>>> I've update two patches today for these issues, could you please test them?
>>> 
>>> On 2018/7/6 9:30, Xu, Wen wrote:
>>>> Thanks very much! I would like to provide any further help or testing.
>>>> 
>>>> -Wen
>>>> 
>>>>> On Jul 5, 2018, at 9:13 PM, Chao Yu <yuchao0@huawei.com> wrote:
>>>>> 
>>>>> Hi Wen,
>>>>> 
>>>>> On 2018/7/6 3:19, Xu, Wen wrote:
>>>>>> Dear F2FS developers,
>>>>>> 
>>>>>> By fuzzing, I find some new issues in Linux f2fs kernel module. Here are the links on Bugzilla,
>>>>>> 
>>>>>> 200419	NULL pointer dereference in __remove_dirty_segment() when mounting an f2fs image
>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=200419
>>> 
>>> https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/commit/?h=f2fs-dev&id=ccf5e1525e92010dd2cb8ff5a820283f9bff5c78
>>> 
>>>>>> 
>>>>>> 200421	Buffer overrun in f2fs_truncate_inline_inode() when umounting an f2fs image
>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=200421
>>> 
>>> https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/commit/?h=f2fs-dev&id=ea08202ee4ca67b31b3510591f2a8032ec3ac4cb
>>> 
>>>>>> 
>>>>>> 200423	Out-of-bound access in f2fs_get_dnode_of_data() when operating file on an f2fs image
>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=200423
>>>>>> 
>>>>>> 200425	Invalid memory access in f2fs_find_target_dentry() when operating files on an f2fs image
>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=200425
>>> 
>>> Fixes this issue with above commit.
>>> 
>>> Thanks,
>>> 
>>>>>> 
>>>>>> Regarding my testing, they can all be reproduced w/ Chao’s f2fs-dev branch. Thanks!
>>>>> 
>>>>> Alright, I will dig into these issues in these days, once I have solution, will
>>>>> let you know.
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>>> 
>>>>>> -Wen
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>> _______________________________________________
>>>> Linux-f2fs-devel mailing list
>>>> Linux-f2fs-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
>> 
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Linux-f2fs-devel mailing list
>> Linux-f2fs-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
>> 

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2018-07-08  2:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05 19:19 Bug report: some new bugs found by fuzzing Xu, Wen
2018-07-06  1:13 ` Chao Yu
2018-07-06  1:30   ` Xu, Wen
2018-07-06  7:00     ` Chao Yu
2018-07-06 13:01       ` Xu, Wen
2018-07-06 16:22     ` Chao Yu
2018-07-07 15:48       ` Xu, Wen
2018-07-07 16:32         ` Chao Yu
2018-07-08  2:43           ` Xu, Wen [this message]
2018-07-09  2:24             ` Chao Yu
2018-07-09 15:10             ` Chao Yu
2018-07-09 19:11               ` Xu, Wen

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=14604831-EB4B-421F-B5E4-BB159611D850@gatech.edu \
    --to=wen.xu@gatech.edu \
    --cc=chao@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: 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;
as well as URLs for NNTP newsgroup(s).