linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Karsten Hopp <karsten@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Patch to support LUKS UUIDs in libblkid
Date: Fri, 8 Jun 2007 11:36:00 -0400	[thread overview]
Message-ID: <20070608153600.GA9726@thunk.org> (raw)
In-Reply-To: <4665479E.2060707@redhat.com>

In addition to the comments already posted:

> +/* check it manually as using LUKS_read_phdr from libcryptsetup
> + * prints too many warnings if it isn't a luks partition and would add a
> + * dependency on the lib */
> +static int probe_luks(struct blkid_probe *probe,
> +		       struct blkid_magic *id __BLKID_ATTR((unused)), 
> +		       unsigned char *buf)
> +{
> +	const char *luks_magic = id->bim_magic;
> +	unsigned char *p_buf = buf;
> +	unsigned char uuid[40];
> +	if(strncmp(buf, luks_magic, strlen(luks_magic)) == 0)   /* ID matches, continue */

There's no point in doing this check, since it's replicating a check
already done in the generic code.  The probe function won't be called
if the bim_magic didn't match the specified offset. 

						- Ted

  parent reply	other threads:[~2007-06-08 22:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-05 11:23 Patch to support LUKS UUIDs in libblkid Karsten Hopp
2007-06-05 14:20 ` Eric Sandeen
2007-06-05 23:17 ` Andreas Dilger
2007-06-08 15:36 ` Theodore Tso [this message]
2007-06-11 11:51   ` Karsten Hopp
2007-06-12 23:40     ` Theodore Tso
2007-06-13 11:00       ` Karsten Hopp
2007-06-21 17:56         ` Theodore Tso
2007-07-03  9:19           ` Karsten Hopp
2007-07-03 15:57             ` Eric Sandeen
     [not found]           ` <46964694.7000707@redhat.com>
2007-07-23 15:00             ` Karsten Hopp
2007-07-23 16:19               ` Theodore Tso

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=20070608153600.GA9726@thunk.org \
    --to=tytso@mit.edu \
    --cc=karsten@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    /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 NNTP newsgroup(s).