linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: "Xu, Wen" <wen.xu@gatech.edu>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: A list of bugs in btrfs found by fuzzing
Date: Wed, 4 Jul 2018 06:36:34 +0800	[thread overview]
Message-ID: <6408ed6e-12c0-c34c-a940-c559e238a212@gmx.com> (raw)
In-Reply-To: <D1C443C6-9EBD-4F4D-B60E-5CC7D22BC3C0@gatech.edu>


[-- Attachment #1.1: Type: text/plain, Size: 3047 bytes --]



On 2018年07月04日 00:27, Xu, Wen wrote:
> So this is the dev branch of btrfs?…

Just my branch of all the related fixes.

Thanks,
Qu

> 
> Thanks,
> -Wen
> 
>> On Jul 3, 2018, at 9:36 AM, Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>
>>
>>
>> On 2018年07月03日 20:37, Xu, Wen wrote:
>>> Sure, thanks for your efforts! So as I suppose, 199833 and 199835 are implicitly fixed by these patches as well?
>>>
>>> -Wen
>>
>> Yep.
>>
>> Kernel can know detect all related chunk <-> block group mapping problem
>> in all 6 images and exit gracefully with error message showing what's
>> going wrong.
>>
>> You could also test using this branch:
>> https://github.com/adam900710/linux/tree/tree_checker_enhance
>>
>> Thanks,
>> Qu
>>
>>
>>>
>>>> On Jul 3, 2018, at 4:32 AM, Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>>>
>>>>
>>>>
>>>> On 2018年07月01日 08:06, Xu, Wen wrote:
>>>>> Dear BTRFS developers,
>>>>>
>>>>> I would like to know if these issues are fixed or handled? Thanks.
>>>>>
>>>>> -Wen
>>>>
>>>> All these images should be addressed by the following patches now:
>>>> https://patchwork.kernel.org/patch/10503415/
>>>> https://patchwork.kernel.org/patch/10503413/
>>>> https://patchwork.kernel.org/patch/10503403/
>>>> https://patchwork.kernel.org/patch/10503147/
>>>> https://patchwork.kernel.org/patch/10503099/
>>>>
>>>> Some of them may need extra cosmetic updates, but the basic fix should
>>>> not change much.
>>>>
>>>> If you have any newer fuzzed image which could pass kernel mount and
>>>> cause unexpected behavior, feel free to submit them to btrfs maillist
>>>> and kernel bugzilla.
>>>>
>>>> Thanks,
>>>> Qu
>>>>
>>>>>
>>>>>> On Jun 3, 2018, at 6:22 PM, Wen Xu <xuwen.sjtu@gmail.com> wrote:
>>>>>>
>>>>>> Hi btrfs maintainers and developers,
>>>>>>
>>>>>> Here are a list of bugs found in upstream kernel recently. Please check:
>>>>>>
>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=199833
>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=199835
>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=199837
>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=199839
>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=199847
>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=199849
>>>>>>
>>>>>> Thanks,
>>>>>> Wen
>>>>>
>>>>> --
>>>>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>>>>> the body of a message to majordomo@vger.kernel.org
>>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>> N�����r��y���b�X��ǧv�^�)޺{.n�+����{�n�߲)���w*\x1fjg���\x1e�����ݢj/���z�ޖ��2�ޙ���&�)ߡ�a��\x7f��\x1e�G���h�\x0f�j:+v���w�٥
> 
> N�����r��y���b�X��ǧv�^�)޺{.n�+����{�n�߲)���w*\x1fjg���\x1e�����ݢj/���z�ޖ��2�ޙ���&�)ߡ�a��\x7f��\x1e�G���h�\x0f�j:+v���w�٥
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-07-03 22:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-03 22:22 A list of bugs in btrfs found by fuzzing Wen Xu
2018-07-01  0:06 ` Xu, Wen
2018-07-01  7:39   ` Qu Wenruo
2018-07-03  8:32   ` Qu Wenruo
2018-07-03 12:37     ` Xu, Wen
2018-07-03 13:36       ` Qu Wenruo
2018-07-03 16:27         ` Xu, Wen
2018-07-03 22:36           ` Qu Wenruo [this message]
2018-07-03 23:26             ` Xu, Wen
2018-07-03 23:38               ` Qu Wenruo
2018-07-04  1:22                 ` 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=6408ed6e-12c0-c34c-a940-c559e238a212@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wen.xu@gatech.edu \
    /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).