Package Details: linux-simple-bcachefs-git 6.2.arch1.r2581-1

Git Clone URL: https://aur.archlinux.org/linux-simple-bcachefs-git.git (read-only, click to copy)
Package Base: linux-simple-bcachefs-git
Description: The Linux kernel and modules with bcachefs support
Upstream URL: https://github.com/archlinux/linux/commits/v6.2-arch1
Licenses: GPL2
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: nightfog
Maintainer: nightfog
Last Packager: nightfog
Votes: 0
Popularity: 0.000000
First Submitted: 2021-10-10 09:54 (UTC)
Last Updated: 2023-03-18 05:44 (UTC)

Required by (4)

Sources (1)

Pinned Comments

nightfog commented on 2021-10-17 14:18 (UTC) (edited on 2023-03-18 06:07 (UTC) by nightfog)

Quick facts about usage:

  1. Filesystem support is build in, no need to mess with modules and initramfs.
  2. On every build the current bcachefs patch is fetched from developer's git tree. So, no need to wait for the package to be updated, you are always up to date.
  3. Besides bcache fs support, there are no other changes to the official Arch Linux kernel.
  4. Upstream patch development is based on mainline kernel. This package is based on the same version of mainline kernel, or the closest stable/testing version available in Arch Linux. This kernel version is not changed unless the upstream decides to switch to a newer one. So if you use this package, you will not receive stable sublevel patches (in notation a.b.c it will always be a.b.0).
  5. When upstream switch from one kernel version to another, there is a lag before the package is updated. The package is not building at this period. Be patient to wait or try to apply the changes if you are in a hurry.
  6. Try to keep the build folder. On next build time it would be much less stuff to fetch.

Latest Comments

nightfog commented on 2023-03-18 05:56 (UTC) (edited on 2023-03-18 05:57 (UTC) by nightfog)

For anyone interested, an updated version is now works for me. This is probably mentioned here https://github.com/koverstreet/bcachefs/issues/520. If you hit this bug, do a kernel recompilation on some other system, boot the broken system with nomem_profiling kernel parameter, go to terminal (disable graphics environment to minimize crash chance) and update the kernel package.

david_rysk commented on 2023-03-17 02:08 (UTC)

I suspect an issue with the patching mechanism; using the process that the linux-bcachefs-git AUR package uses would likely be more reliable. That process involves fetching from the bcachefs remote and merging it over top of the arch kernel git checkout.

nightfog commented on 2023-03-16 17:04 (UTC)

I've hit this too. It seems to be related to some debugging options being enabled by default in bcachefs tree. As a quick fix try to add a kernel parameter 'nomem_profiling'. I'll be glad to get a feedback. I will check for permanent fix in coming days.

david_rysk commented on 2023-03-15 00:53 (UTC) (edited on 2023-03-15 02:52 (UTC) by david_rysk)

This seems to miscompile the kernel for me, leading to many KFENCE use-after-free errors. This does not happen with the linux-bcachefs-git AUR package.

nightfog commented on 2021-10-17 14:18 (UTC) (edited on 2023-03-18 06:07 (UTC) by nightfog)

Quick facts about usage:

  1. Filesystem support is build in, no need to mess with modules and initramfs.
  2. On every build the current bcachefs patch is fetched from developer's git tree. So, no need to wait for the package to be updated, you are always up to date.
  3. Besides bcache fs support, there are no other changes to the official Arch Linux kernel.
  4. Upstream patch development is based on mainline kernel. This package is based on the same version of mainline kernel, or the closest stable/testing version available in Arch Linux. This kernel version is not changed unless the upstream decides to switch to a newer one. So if you use this package, you will not receive stable sublevel patches (in notation a.b.c it will always be a.b.0).
  5. When upstream switch from one kernel version to another, there is a lag before the package is updated. The package is not building at this period. Be patient to wait or try to apply the changes if you are in a hurry.
  6. Try to keep the build folder. On next build time it would be much less stuff to fetch.