From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-fs/bees/
Date: Mon, 10 Jul 2023 03:53:21 +0000 (UTC) [thread overview]
Message-ID: <1688961175.f877f81191289a416cdc79a4782abd42f13a1b85.sam@gentoo> (raw)
commit: f877f81191289a416cdc79a4782abd42f13a1b85
Author: Kai Krakow <kai <AT> kaishome <DOT> de>
AuthorDate: Mon Feb 27 00:44:57 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Jul 10 03:52:55 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f877f811
sys-fs/bees: update 9999
The statement about using bees with kernel 5.4 or later is no longer
true for bees as it serializes the kernel calls since December 2022. The
kernel itself still suffers from the bug, tho. But that's not business
of the bees ebuild.
Signed-off-by: Kai Krakow <kai <AT> kaishome.de>
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-fs/bees/bees-9999.ebuild | 8 --------
1 file changed, 8 deletions(-)
diff --git a/sys-fs/bees/bees-9999.ebuild b/sys-fs/bees/bees-9999.ebuild
index f84aba717799..65c3cbecea85 100644
--- a/sys-fs/bees/bees-9999.ebuild
+++ b/sys-fs/bees/bees-9999.ebuild
@@ -66,14 +66,6 @@ pkg_pretend() {
ewarn "https://github.com/Zygo/bees/blob/master/docs/btrfs-kernel.md"
ewarn
fi
- if kernel_is -ge 5 4 0; then
- ewarn "With kernel version 5.4 or later, the kernel may hang when multiple threads"
- ewarn "are running LOGICAL_INO and dedupe ioctl. This is not exclusively triggered"
- ewarn "by bees but also other software running such operations, bees will just more"
- ewarn "likely trigger this bug. You can work around this issue by reducing the"
- ewarn "thread count of bees to 1."
- ewarn
- fi
elog "Bees recommends running the latest current kernel for performance and"
elog "reliability reasons, see README.md."
next reply other threads:[~2023-07-10 3:53 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 3:53 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-20 3:36 [gentoo-commits] repo/gentoo:master commit in: sys-fs/bees/ Sam James
2025-01-20 3:36 Sam James
2025-01-20 3:36 Sam James
2024-12-01 16:15 Sam James
2024-08-08 14:12 Joonas Niilola
2023-12-28 14:58 Sam James
2023-09-27 10:11 Joonas Niilola
2023-07-10 3:54 Sam James
2023-07-10 3:53 Sam James
2023-07-10 3:53 Sam James
2023-07-10 3:53 Sam James
2023-07-07 2:20 Sam James
2023-02-09 13:33 Joonas Niilola
2023-02-09 13:33 Joonas Niilola
2023-02-09 13:33 Joonas Niilola
2023-02-09 13:33 Joonas Niilola
2023-02-09 13:33 Joonas Niilola
2022-12-17 19:33 Sam James
2022-12-17 19:33 Sam James
2022-12-17 19:33 Sam James
2022-12-17 19:33 Sam James
2022-05-30 7:38 Sam James
2021-07-09 0:11 Ionen Wolkens
2021-07-07 18:47 Ionen Wolkens
2021-07-07 18:47 Ionen Wolkens
2021-01-04 13:56 Joonas Niilola
2021-01-04 13:56 Joonas Niilola
2020-11-07 20:04 Sam James
2019-11-30 7:50 Joonas Niilola
2019-11-30 7:50 Joonas Niilola
2019-11-28 16:34 Joonas Niilola
2019-11-28 16:34 Joonas Niilola
2019-06-18 5:40 Michał Górny
2019-06-18 5:40 Michał Górny
2018-10-01 8:01 Georgy Yakovlev
2018-10-01 8:01 Georgy Yakovlev
2018-09-29 20:08 Michał Górny
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=1688961175.f877f81191289a416cdc79a4782abd42f13a1b85.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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