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 10:07:15 -0400 [thread overview]
Message-ID: <20240905140715.GV9627@mit.edu> (raw)
In-Reply-To: <2e4f662b-2c52-4148-afea-0f7d09d2776b@huawei.com>
On Thu, Sep 05, 2024 at 09:31:35PM +0800, Baokun Li wrote:
> > > 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
> >
> OK, I didn't know it was pulling automatically, thanks for the explanation!
Yep, and some of us have automated test systems that run whenever
fs-next is updated. :-)
For example, see attached. (I have been planning to get this
published someplace, such as a linux.linux.dev list, but I've been too
busy finish up making it be fully robust and not subject to rare
failures that require manual interventions, and I need to complete
some negotiations with Konstantin. Probably after the Linux Plumbers
Conference and I have a bit more free time...)
- Ted
TESTRUNID: ltm-20240729133952-0028
KERNEL: kernel 6.11.0-rc6-xfstests-00781-g8d32ae66515d #1 SMP PREEMPT_DYNAMIC Wed Sep 4 21:56:52 EDT 2024 x86_64
CMDLINE: -c ext4/all,xfs/all,btrfs/all,f2fs/all -g auto --repo https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next --watch fs-next
CPUS: 2
MEM: 7680
ext4/4k: 570 tests, 2 failures, 51 skipped, 5668 seconds
Flaky: generic/234: 20% (1/5) generic/277: 20% (1/5)
ext4/1k: 564 tests, 2 failures, 54 skipped, 6139 seconds
Failures: generic/627 generic/750
ext4/ext3: 562 tests, 144 skipped, 4388 seconds
ext4/encrypt: 545 tests, 167 skipped, 3169 seconds
ext4/nojournal: 562 tests, 122 skipped, 4013 seconds
ext4/ext3conv: 567 tests, 53 skipped, 5500 seconds
ext4/adv: 563 tests, 2 failures, 59 skipped, 5186 seconds
Flaky: generic/047: 20% (1/5) generic/547: 20% (1/5)
ext4/dioread_nolock: 568 tests, 51 skipped, 5108 seconds
ext4/data_journal: 563 tests, 127 skipped, 4489 seconds
ext4/bigalloc_4k: 541 tests, 1 failures, 55 skipped, 4766 seconds
Flaky: generic/320: 60% (3/5)
ext4/bigalloc_1k: 542 tests, 64 skipped, 4814 seconds
ext4/dax: 556 tests, 157 skipped, 3022 seconds
xfs/4k: 1142 tests, 2 failures, 180 skipped, 10178 seconds
Failures: generic/754 xfs/432
xfs/1k: 1142 tests, 3 failures, 167 skipped, 14218 seconds
Failures: generic/627 generic/754 xfs/432
xfs/v4: 1141 tests, 2 failures, 474 skipped, 8851 seconds
Failures: generic/754 xfs/432
xfs/adv: 1142 tests, 2 failures, 166 skipped, 10238 seconds
Failures: generic/754 xfs/432
xfs/quota: 1142 tests, 2 failures, 165 skipped, 11276 seconds
Failures: generic/754 xfs/432
xfs/quota_1k: 1142 tests, 3 failures, 167 skipped, 13616 seconds
Failures: generic/627 generic/754 xfs/432
xfs/dirblock_8k: 1142 tests, 2 failures, 165 skipped, 11244 seconds
Failures: generic/754 xfs/432
xfs/realtime: 1141 tests, 4 failures, 518 skipped, 8342 seconds
Failures: generic/260 generic/455 generic/754 xfs/432
xfs/realtime_28k_logdev: 1141 tests, 4 failures, 600 skipped, 12882 seconds
Failures: generic/260 generic/754 xfs/432 xfs/598
xfs/realtime_logdev: 1141 tests, 4 failures, 572 skipped, 13036 seconds
Failures: generic/260 generic/754 xfs/432 xfs/598
xfs/logdev: 1142 tests, 3 failures, 235 skipped, 17787 seconds
Failures: generic/754 xfs/432 xfs/598
xfs/dax: 1152 tests, 1 failures, 551 skipped, 5930 seconds
Failures: generic/754
btrfs/default: 1038 tests, 4 failures, 278 skipped, 9576 seconds
Failures: btrfs/012 btrfs/277
Flaky: generic/418: 20% (1/5) generic/746: 40% (2/5)
f2fs/default: 720 tests, 7 failures, 245 skipped, 5432 seconds
Failures: generic/050 generic/064 generic/252 generic/563 generic/735
Flaky: f2fs/004: 20% (1/5) generic/475: 40% (2/5)
f2fs/encrypt: 702 tests, 4 failures, 352 skipped, 3064 seconds
Failures: generic/050 generic/563 generic/635
Flaky: generic/475: 20% (1/5)
Totals: 23089 tests, 5942 skipped, 234 failures, 0 errors, 197866s
FSTESTIMG: gce-xfstests/xfstests-amd64-202408121130
FSTESTPRJ: gce-xfstests
FSTESTVER: blktests f043065 (Thu, 20 Jun 2024 16:26:22 +0900)
FSTESTVER: fio fio-3.36 (Fri, 20 Oct 2023 04:30:43 -0600)
FSTESTVER: fsverity v1.6 (Wed, 20 Mar 2024 21:21:46 -0700)
FSTESTVER: ima-evm-utils v1.5 (Mon, 6 Mar 2023 07:40:07 -0500)
FSTESTVER: libaio libaio-0.3.108-82-gb8eadc9 (Thu, 2 Jun 2022 13:33:11 +0200)
FSTESTVER: ltp 20240524-131-gdfb293ee0 (Mon, 29 Jul 2024 09:57:32 +0200)
FSTESTVER: nvme-cli v1.16 (Thu, 11 Nov 2021 13:09:06 -0800)
FSTESTVER: quota v4.05-67-g8254bec (Mon, 29 Jul 2024 12:24:36 -0400)
FSTESTVER: util-linux v2.40 (Wed, 27 Mar 2024 12:46:59 +0100)
FSTESTVER: xfsprogs v6.9.0 (Mon, 22 Jul 2024 11:05:03 +0200)
FSTESTVER: xfstests-bld 8456529b (Wed, 31 Jul 2024 22:17:54 -0400)
FSTESTVER: xfstests v2024.08.11-7-gc3fc1ccce-dirty (Mon, 12 Aug 2024 11:25:51 -0400)
FSTESTVER: zz_build-distro bookworm
FSTESTSET: -g auto
FSTESTOPT: aex
next prev parent reply other threads:[~2024-09-05 14:07 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
2024-09-05 13:31 ` Baokun Li
2024-09-05 14:07 ` Theodore Ts'o [this message]
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=20240905140715.GV9627@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.