From: "Theodore Ts'o" <tytso@mit.edu>
To: Baokun Li <libaokun1@huawei.com>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
lkp@intel.com, oe-kbuild-all@lists.linux.dev,
Jan Kara <jack@suse.cz>,
oe-kbuild@lists.linux.dev, Ojaswin Mujoo <ojaswin@linux.ibm.com>,
Yang Erkun <yangerkun@huawei.com>
Subject: Re: [linux-next:master 8348/9291] fs/ext4/extents.c:6155 ext4_ext_clear_bb() error: double free of 'path'
Date: Thu, 5 Sep 2024 09:23:35 -0400 [thread overview]
Message-ID: <20240905132335.GT9627@mit.edu> (raw)
In-Reply-To: <c2711f3d-6bee-414c-952f-5c33da315a1a@huawei.com>
On Thu, Sep 05, 2024 at 09:30:37AM +0800, Baokun Li wrote:
> Now Ted has fixed this problem in his branch:
> https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?h=dev&id=2352e3e461926b59f01c1e39fbb0494891cff997
>
> Ted, could you please help push the corrected commit to the next branch?
The next branch gets automatically refreshed every day (Mondays
through Friday). In the case of the ext4 tree, it gets picked up from
the dev branch. So it should be fixed in the upcoming fs-next and
linux-next branch.
Cheers,
- Ted
next prev parent reply other threads:[~2024-09-05 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 17:39 [linux-next:master 8348/9291] fs/ext4/extents.c:6155 ext4_ext_clear_bb() error: double free of 'path' Dan Carpenter
2024-09-05 1:30 ` Baokun Li
2024-09-05 13:23 ` Theodore Ts'o [this message]
2024-09-05 13:31 ` Baokun Li
2024-09-05 14:07 ` Theodore Ts'o
2024-09-06 1:26 ` Baokun Li
-- strict thread matches above, loose matches on Subject: below --
2024-09-04 16:51 kernel test robot
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=20240905132335.GT9627@mit.edu \
--to=tytso@mit.edu \
--cc=dan.carpenter@linaro.org \
--cc=jack@suse.cz \
--cc=libaokun1@huawei.com \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
--cc=ojaswin@linux.ibm.com \
--cc=yangerkun@huawei.com \
/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 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.