From: Ondrej Kozina <okozina@redhat.com>
To: Surmont Jasper <jasper.surmont@aalto.fi>,
"cryptsetup@lists.linux.dev" <cryptsetup@lists.linux.dev>
Subject: Re: Lib and Src directory
Date: Mon, 4 Apr 2022 11:05:25 +0200 [thread overview]
Message-ID: <70ae3ef5-85dd-56bb-eebb-1e6f3f502534@redhat.com> (raw)
In-Reply-To: <PR3P192MB1087367FCDE3417198711049F1E59@PR3P192MB1087.EURP192.PROD.OUTLOOK.COM>
On 04. 04. 22 10:46, Surmont Jasper wrote:
> Hey, newbie question here:
>
> What is the interpretation between the src/ and lib/ directory?
The /lib directory contains source code for libcryptsetup library.
The /src contains sources for all cryptsetup project maintained command
line utilities: cryptsetup, integritysetup and veritysetup.
> For example, I see files like integrity.c or verity.c etc. Are these files also files written for the cryptsetup project,
> or do these contain the same code that can be found in the linux kernel /drivers/md/dm-integrity.c for example?
Yes. It's internal libcryptsetup code. For example the integrity.c in
lib/integrity directory contains code for managing dm-integrity kernel
driver (DM target). The low level access to DM kernel drivers is done
via the libdevmapper library which the libcryptsetup links with.
Libdevmapper is maintained by lvm2 project.
Regards
O.
prev parent reply other threads:[~2022-04-04 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 8:46 Lib and Src directory Surmont Jasper
2022-04-04 9:05 ` Ondrej Kozina [this message]
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=70ae3ef5-85dd-56bb-eebb-1e6f3f502534@redhat.com \
--to=okozina@redhat.com \
--cc=cryptsetup@lists.linux.dev \
--cc=jasper.surmont@aalto.fi \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).