Debian Patches

Status for openafs/1.8.14-1

Patch Description Author Forwarded Bugs Origin Last update
0003-Catch-up-to-roken-s-rename-of-base64-symbols.patch Catch up to roken's rename of base64 symbols
Upstream roken (i.e., heimdal) renamed their base64 encode/decode
routines to have a rk_ prefix in 2014, but upstream OpenAFS hasn't
pulled in an update to their bundled heimdal files since then.
So, upstream is still using the old name, whereas we are trying
to link against a more modern libroken, and must use the new names.		 Benjamin Kaduk <kaduk@mit.edu> no 2016-12-11
0007-Temporarily-disable-flaky-test.patch Temporarily disable flaky test
The volser test consistently fails on the armhf buildd but succeeds
on the porterbox. The nature of the test in question suggests that
the issue in the test triggers only on a machine with a specific
network configuration using specific addresses in 10.0.0.0/8, which
should help track down the issue causing the test to fail on the buildd.		 Benjamin Kaduk <kaduk@mit.edu> no 2020-03-24
0014-build-clean-up-some-more-generated-files.patch build: clean up some more generated files
Commit c1d39153da00d5525b2f7874b2d214a7f1b1bb86 added a cc-wrapper
script to help generate CTF data for all objects, which is generated
by configure. Remove it in the distclean target so we don't leave
a stray file hanging around.

Commit 48ce41a447c354b8a20b769e4aa5b502ba5bcc09 added a pkgbuild.sh
script, to be used to build packages for newer versions of macOS,
supplementing the buildpkg.sh that was previously used. Clean it
up in distclean as well (buildpkg.sh was already listed).

Also clean up AFS_component_version_number.c in
libuafs/Makefile.common.in.

These issues were detected while resolving
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1048470 .		 Benjamin Kaduk <kaduk@mit.edu> no 2023-12-22
0004-Linux-Use-struct-kiocb-for-aops-write_begin-end.patch Linux: Use struct kiocb * for aops write_begin/end
The Linux 6.17 commit:
fs: change write_begin/write_end interface to take struct kiocb *
(e9d8e2bf23206)
changed the address_space_operations members write_begin and write_end
to use a 'struct kiocb *' instead of a 'struct file *' as the first
parameter.

The passed kiocb structure contains a pointer (ki_filp) to the file
structure that is associated with the operation.

Update the afs_linux_write_begin() and afs_linux_write_end() to accept
a 'struct kiocb *' instead of a 'struct file *', and obtain the file
pointer directly from kiocb.

Add an autoconf test to determine if aops->write_begin()/aops->write_end
uses a struct kiocb * as the first parameter.

(cherry picked from commit 1ad827ded0ed970540b6836250f2395ae31b84bc)

(cherry picked from commit a765a9ddd412c8d1e5cb0f5cf497a8606251811e)		 Cheyenne Wills <cwills@sinenomine.net> no 2025-10-21
0005-linux-remove-implied-def-HAVE_LINUX_FILEMAP_GET_FOLI.patch linux: remove implied def HAVE_LINUX_FILEMAP_GET_FOLIO
Commit:
Linux: Use struct kiocb * for aops write_begin/end (1ad827ded0ed9)
added 2 implied defines in osi_vnodeops, one for
HAVE_LINUX_WRITE_BEGIN_END_FOLIO and one for HAVE_LINUX_FILEMAP_GET_FOLIO.
The HAVE_LINUX_FILEMAP_GET_FOLIO was not needed, and causes a build
failure:

osi_vnodeops.c:4056:10: error: "HAVE_LINUX_FILEMAP_GET_FOLIO" redefined [-Werror]
4056 | # define HAVE_LINUX_FILEMAP_GET_FOLIO
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~

This is because the configure test for __filemap_get_folio() succeeds
(linux 6.15 and later) and the test for write_begin/end functions take a
kiocb also succeeds (6.17 or later).

Remove the unnecessary define.

(cherry picked from commit 503ef823970695eb646a323f38b9c07d52971e69)

(cherry picked from commit c379ff006d8b7db425f7648321c549ab24919d92)		 Cheyenne Wills <cwills@sinenomine.net> no 2025-10-23

All known versions for source package 'openafs'

Links