Posts
4491
Following
316
Followers
475
Linux kernel hacker and maintainer etc.

OpenPGP: 3AB05486C7752FE1
@ljs @hyeyoo @lkundrak I'd like to run the self-test on the hardware. Can you point to the branch containing the patches, I can add a remote.
1
0
0

Jarkko Sakkinen

Edited 9 months ago
@ljs @hyeyoo @lkundrak I was breathing life back to NUC7CJYH with to be a kernel testing target and needed some random kernel patches to feed and this came in Mastodon, thus the collision ;-) Feel free to CC the patch set tho (next version with a kselftest). Right and one review comment: put the baseline commit ID or tag to the cover letter

It's an old NUC with the most inefficient Celeron CPU one could imagine, incoherent mixture of hardware feature from both desktop and server lineups and generally super shitty x86 from Intel. Thus, has been my main target for years if QEMU won't do...
1
0
0
@ljs @lkundrak @hyeyoo

there's a glitch:

Applying: mm: pagewalk: add the ability to install PTEs
Applying: mm: add PTE_MARKER_GUARD PTE marker
Applying: mm: madvise: implement lightweight guard page mechanism
Applying: selftests/mm: add self tests for guard page feature
error: sha1 information is lacking or useless (tools/testing/selftests/mm/.gitignore).
error: could not build fake ancestor
Patch failed at 0004 selftests/mm: add self tests for guard page feature
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"

HEAD is v6.12-rc4
1
0
0

Jarkko Sakkinen

Updated, added back a klog message and some cc spread. The bug triples boot time on at least some #AMD machine but I guess it does not matter 🤷

https://lore.kernel.org/linux-integrity/20241021053921.33274-1-jarkko@kernel.org/

#linux #kernel
0
1
2
not there yet plus no zsh auto-completion
0
0
0

Jarkko Sakkinen

this quite a nice alt client for pass: https://github.com/timvisee/prs
1
0
0

Jarkko Sakkinen

KICK3 is quite bad. I already disliked previously in KICK2 the on-board effects, and it add only more of that cruft. Less features is also a feature I guess :-) ... and it looks damn ugly too. KickDrum is more fresh and the harmonic EQ is great in it: https://audija.com/plugins #Bitwig #BitwigStudio #MusicProduction
0
0
1

Jarkko Sakkinen

Could it be that #clevis has a bug that the following ends up failing unless the passphrase is non-empty?

sudo clevis luks bind -d /dev/nvme... tpm2 '{"pcr_ids":"1,4,5,7,9"}'

An empty passphrase can be created by the means of:

sudo cryptsetup luksChangeKey --force-password /dev/sda3

It is a totally legit configuration for NUC7CJYH, which I use for kernel testing.

#fedora

1
0
0
@vbabka i've tried some more advanced but this is what i actually use, from kernel patch sets to grocery shopping lists. unfortunately you're most likely right. people don't seem to like functional web apps 🤷
0
0
1

Jarkko Sakkinen

best thing #google has ever made is imho #keep. i use it organize all my patch sets etc.
1
0
0
aerc/msmtp/mbsync/pass is how I roll my email :-) after years and years of polishing...
0
0
0
For folder-map I have a bit different application. I have shared my email account with my personal and kernel identities, and I use it to swap the INBOX as:

personal = INBOX
INBOX = kernel

A sieve filter in the email server puts all the @kernel.org email into "kernel". Otherwise, I have both accounts pointing to same Maildir folder with different identities and msmtp command-lines (e.g. "outgoing = msmtp -a kernel.org").
1
0
0

Jarkko Sakkinen

my de-facto always repeated comment about Linux kernel and Rust ;-) It is how it is...

https://lwn.net/Articles/994778/

#Linux #kernel #Rust
0
1
3
It'd be easy to script "---" append but so far I've just manually added the dashes because it is good final checkpoint before "git send-email". I like to keep some steps purposely manual instead of automating just to get a final look.
0
0
1

Jarkko Sakkinen

This is how I've managed #patch change logs for some years already:

https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/commit/?h=hmac-v6&id=b45ca8b0b88c265a77579d18b2fa8c297433560e

I just add three dashes to each patch to the empty space just before the change log. It's a trick I learned originally from Dave Hansen some years ago and have used since.

Wonder how others cope with the same problem.

#linux #kernel
1
1
0
article was cool too, i learned to color ML's :-)
1
0
1

Jarkko Sakkinen

#aerc user since somewhere 2022. it's great https://lwn.net/Articles/993498/ #email
1
0
1
Show older