Sure, thanks for your efforts! So as I suppose, 199833 and 199835 are implicitly fixed by these patches as well? -Wen > On Jul 3, 2018, at 4:32 AM, Qu Wenruo <quwenruo.btrfs@xxxxxxx> 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@xxxxxxxxx> 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@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html ��.n��������+%������w��{.n�����{����n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
