linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Karsten Hopp <karsten@redhat.com>
Cc: Theodore Tso <tytso@mit.edu>,
	linux-ext4@vger.kernel.org, dm-crypt@saout.de
Subject: Re: Patch to support LUKS UUIDs in libblkid
Date: Tue, 03 Jul 2007 10:57:57 -0500	[thread overview]
Message-ID: <468A7205.4010509@redhat.com> (raw)
In-Reply-To: <468A149B.60700@redhat.com>

Karsten Hopp wrote:

> Thanks for applying the small patch !
> 
> FYI:
> I've opened a bugzilla about your udev concerns to get some comments from our
> and the upstream maintainer at
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=245717
> 
> Kay Sievers from the udev team responded:
> #> That's nothing new. Guessing filesystems by magic bytes on the disk is by
> #> definition unsafe.
> #>
> #> _All_ filesystem formatters are required to wipe out _all_ existing signatures
> #> before applying a new signature. Even then, it's not entirely safe to probe, but
> #> we obviously have no alternatives.

We fought this for a while in xfs, trying to be sure we wipe out old fs
signatures at mkfs time.  It'd be nice to have a library to do such
things...

-Eric

  reply	other threads:[~2007-07-03 16:00 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
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 [this message]
     [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=468A7205.4010509@redhat.com \
    --to=sandeen@redhat.com \
    --cc=dm-crypt@saout.de \
    --cc=karsten@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).