From: Martin Steigerwald <martin@lichtvoll.de>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: AP <lkml@inml.grue.cc>, linux-bcachefs@vger.kernel.org
Subject: Re: Error while unlocking encrypted BCacheFS: Required key not available
Date: Thu, 11 Jan 2024 19:23:45 +0100 [thread overview]
Message-ID: <1876779.tdWV9SEqCh@lichtvoll.de> (raw)
In-Reply-To: <vm333u3hnogd2fz4zk6g4rhkj7rwk27tv2iacacsyjctxkcpvo@bihvvnluk3em>
Kent Overstreet - 11.01.24, 17:35:10 CET:
> I just made a couple suggestions. I'm sorry if they weren't exactly what
> you were looking for?
>
> If you or someone else wants to help out by writing some code, I just
> laid out what needs to happen next - but I'm not your free helpdesk
> here, and you're expecting an imediate fix that's not how this works :)
That is a misunderstanding. I am not expecting an immediate fix or a fix at
all. I did not write I do either. So please do not read something into
what I wrote that simply is not there.
My programming experience in C is more than 20 years old, certainly not
kernel related and not even on the Linux platform and I thought there
might be something I as an user might try to at least pin-point the cause
of this issue a bit more. Apparently there is not and that is okay with
me.
Nothing of what I do with BCacheFS has immediate urgency at the moment.
--
Martin
next prev parent reply other threads:[~2024-01-11 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 11:22 Error while unlocking encrypted BCacheFS: Required key not available Martin Steigerwald
2024-01-07 11:27 ` Martin Steigerwald
2024-01-10 2:13 ` AP
2024-01-10 14:18 ` Martin Steigerwald
2024-01-10 19:13 ` Kent Overstreet
2024-01-11 11:58 ` Martin Steigerwald
2024-01-11 16:35 ` Kent Overstreet
2024-01-11 18:23 ` Martin Steigerwald [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-16 17:59 George Hilliard
2024-01-16 18:20 ` Martin Steigerwald
2024-02-10 18:34 ` Martin Steigerwald
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=1876779.tdWV9SEqCh@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=lkml@inml.grue.cc \
/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