=== leftyfb_ is now known as leftyfb
=== fling is now known as swing
=== swing is now known as bedroller
=== bedroller is now known as fling
[08:15] <xnox> fling:  git fetch --tags ?
[08:16] <xnox> git doesn't fetch unreferenced tags by default, which is pain
[09:27] <fling> xnox: right, had to refetch the tags
[09:27] <fling> for some reason fetched a bunch of objects too
[09:36] <xnox> fling:  this is because we rebase our branches. thus those tags are "dead-ends" from git point of view.
[09:38] <fling> ah ok makes sense
[09:39] <fling> what are the worst "features" of 5.18 release btw?
[09:59] <plappermaul> Does anybody know if kernel irq_mask()/irq_unmask() functions are per cpu/core or system-wide?
[10:03] <xnox> fling:  the bit that it has never been released as ubuntu kernel, and thus likely did not pass certification & regression testing, thus it probably has many issues and regressions.
=== lan3y is now known as laney
[10:21] <fling> xnox: where can I read about this?
[10:40] <xnox> fling:  it's unknown. because we never completed v5.18 integration.
[10:41] <xnox> fling:  and even v5.19 is yet to migrate in kinetic, but it is very close to be ready.
[10:42] <xnox> fling:  but like in a few weeks we will start to have v5.19 in jammy too. why do you desire v5.18?
[15:09] <fling> xnox: wanted to try something newer but 5.19 is not supported by zfs yet
[15:09] <fling> no 2.1.6 patchset yet
[15:27] <xnox> fling:  ubuntu builds zfs in by default... our v5.19 linux kernel in kinetic-proposed is v5.19 based; with all the patches; and zfs built in.....
[15:28] <xnox> fling:  if you want bleeding edge stuff use kinetic + only kernel from proposed https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed 
[15:28] <fling> no 5.19 support in zfs yet 
[15:28] <fling> can go with master though
[15:28] <xnox> (enabling all of kinetic-proposed in development release is harmful)
[15:29] <xnox> ubuntu's kenrel has zfs built in...
[15:30] <xnox> we have https://launchpad.net/ubuntu/+source/zfs-linux/2.1.5-1ubuntu2 which builds with v5.19 and is vendored into our v5.19 kernel https://launchpad.net/ubuntu/+source/linux/5.19.0-15.15
[15:31] <xnox> ./lib/modules/5.19.0-15-generic/kernel/zfs/zfs.ko is there....
[15:55] <fling> are you cherry picking 5.19 compat patches there?
[15:56] <fling> sure it builds and works even without them but there are issues
[16:03] <Eickmeyer> fling: The kernel team knows what they're doing. The kernels they produce undergo extensive testing on dozens of computers in a test lab before they're released to the public.
[16:11] <fling> ubuntu had non-matching userspace/kmod zfs versions
[16:12] <fling> this is not recommended especially before zfs 2 release
[16:13] <Eickmeyer> Does that cause functional issues?
[16:14] <fling> yes this could lead to silent pool corruptions :<
[16:14] <Eickmeyer> But does it?
[16:14] <Eickmeyer> Do you have evidence?
[16:14] <Eickmeyer> Concrete, reproducible evidence?
[16:15] <fling> I'm not an expert in running non-matching versions but there are people in #zfsonlinux with more knowledge on the topic
[16:16] <fling> I'm the errata guy :D
[16:17] <Eickmeyer> Here's the thing:  "not recommended" by upstream does *not* justify it being a bug or wrong. Therefore, your argument is invalid.
[16:17]  * fling noted
[16:23] <xnox> fling:  if you use kinetic, it has matching userspace and kernel zfs version, as all of it is built from the same source package 2.1.5-1ubuntu2
[16:24] <fling> good to know
=== kees_ is now known as kees
[21:11] <hallyn> where's the ubuntu-jammy kernel source git tree these days?  
[21:14] <sarnold> hallyn: I think git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
[21:22] <hallyn> thanks sarnold