From: Christophe Leroy <christophe.leroy@c-s.fr>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [Bug 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten
Date: Fri, 16 Aug 2019 16:59:24 +0200 [thread overview]
Message-ID: <e20943a9-d1a5-0a49-9917-e7b31674c703@c-s.fr> (raw)
In-Reply-To: <bug-204371-206129-GvRQpDzlfW@https.bugzilla.kernel.org/>
Le 16/08/2019 à 16:38, bugzilla-daemon@bugzilla.kernel.org a écrit :
> https://bugzilla.kernel.org/show_bug.cgi?id=204371
>
> --- Comment #34 from Erhard F. (erhard_f@mailbox.org) ---
> On Fri, 16 Aug 2019 08:22:31 +0000
> bugzilla-daemon@bugzilla.kernel.org wrote:
>
>> https://bugzilla.kernel.org/show_bug.cgi?id=204371
>>
>> --- Comment #32 from Christophe Leroy (christophe.leroy@c-s.fr) ---
>> Then see if the WARNING on kfree() in btrfs_free_dummy_fs_info() is still
>> there.
> With latest changes there are no complaints of the kernel any longer. btrfs
> selftests pass, mounting and unmounting a btrfs partition works without any
> suspicious dmesg output.
>
That's good news. Will you handle submitting the patch to BTRFS file
system ?
next parent reply other threads:[~2019-08-16 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-204371-206129@https.bugzilla.kernel.org/>
[not found] ` <bug-204371-206129-GvRQpDzlfW@https.bugzilla.kernel.org/>
2019-08-16 14:59 ` Christophe Leroy [this message]
[not found] <bug-204371-206035@https.bugzilla.kernel.org/>
[not found] ` <bug-204371-206035-3TOBxXIdie@https.bugzilla.kernel.org/>
2019-08-09 12:31 ` [Bug 204371] BUG kmalloc-4k (Tainted: G W ): Object padding overwritten Michael Ellerman
[not found] ` <bug-204371-206035-O9m4mwJN9f@https.bugzilla.kernel.org/>
2019-08-17 8:09 ` christophe leroy
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=e20943a9-d1a5-0a49-9917-e7b31674c703@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/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).