linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: LifeDrive filsystem probe fails [mjg59@srcf.ucam.org: Re:
Date: Thu, 20 Nov 2008 13:17:06 +0000	[thread overview]
Message-ID: <20081120131706.GH2961@nb.net.home> (raw)
In-Reply-To: <20081111142943.GB18544@zigg.com>

On Thu, Nov 13, 2008 at 08:01:34PM +0100, Kay Sievers wrote:
> I've committed  these changes to volume_id, and FAT32 accepts
> completely empty fsinfo signatures now.

 Thanks.

> We always probe for all filesystem types on volumes larger than a
> floppy disk. If we find multiple signatures and one of the detected
> filesystem types specifies that it can no co-exist with another known
> filesystem, like swap and FAT, we do not return a probing result.

 I see the patch (volume_id_probe_filesystem()) and a few things come
 to mind:

  - shouldn't be the relevant parts (label, uuid, version, ...) of
    the "struct volume_id" zeroized when you found a signature and
    before you call the next probing function?

  - it seems as overkill to use two for()s and probe two times for all
    filesystems. What about to store the first result and re-use it?

  - .. or at least never use the second for() when the fist for() found
    nothing ;-)

 For example see the patch below (it's incomplete, volume_id_cpy() and
 volume_id_remresult() are not implemented).

    Karel


diff --git a/extras/volume_id/lib/volume_id.c b/extras/volume_id/lib/volume_id.c
index aaa15e1..0f5cf2d 100644
--- a/extras/volume_id/lib/volume_id.c
+++ b/extras/volume_id/lib/volume_id.c
@@ -421,9 +421,12 @@ int volume_id_probe_filesystem(struct volume_id *id, uint64_t off, uint64_t size
 	 * smaller than a usual floppy disk.
 	 */
 	if (size > 1440 * 1024) {
+		struct volume_id first;
 		int found = 0;
 		int force_unique_result = 0;
 
+		memset(&first, 0, sizeof(first));
+
 		for (i = 0; i < ARRAY_SIZE(prober_filesystem); i++) {
 			int match;
 
@@ -437,20 +440,26 @@ int volume_id_probe_filesystem(struct volume_id *id, uint64_t off, uint64_t size
 					return -1;
 				}
 				found = 1;
+				volume_id_cpy(&first, id);
+				volume_id_remresult(id);
 			}
 		}
+		if (found) {
+			volume_id_cpy(id, &first);
+			goto found;
+		}
+		return -1;
 	}
 
 	/* return the first match */
 	for (i = 0; i < ARRAY_SIZE(prober_filesystem); i++) {
-		if (prober_filesystem[i].prober(id, off, size) = 0) {
-			info("signature '%s' detected\n", id->type);
+		if (prober_filesystem[i].prober(id, off, size) = 0)
 			goto found;
-		}
 	}
 	return -1;
 found:
 	/* If recognized, we free the allocated buffers */
+	info("signature '%s' detected\n", id->type);
 	volume_id_free_buffer(id);
 	return 0;
 }

-- 
 Karel Zak  <kzak@redhat.com>

  parent reply	other threads:[~2008-11-20 13:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 14:29 LifeDrive filsystem probe fails [mjg59@srcf.ucam.org: Matt Behrens
2008-11-11 15:40 ` LifeDrive filsystem probe fails [mjg59@srcf.ucam.org: Re: LifeDrive and T|X not seen by hal] Kay Sievers
2008-11-11 15:47 ` Matthew Garrett
2008-11-13 12:55 ` LifeDrive filsystem probe fails [mjg59@srcf.ucam.org: Karel Zak
2008-11-13 13:40 ` LifeDrive filsystem probe fails [mjg59@srcf.ucam.org: Re: LifeDrive and T|X not seen by hal] Kay Sievers
2008-11-13 15:07 ` Kay Sievers
2008-11-13 19:01 ` Kay Sievers
2008-11-20 13:17 ` Karel Zak [this message]
2008-11-20 14:50 ` Kay Sievers
2008-11-21  9:55 ` Kay Sievers

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=20081120131706.GH2961@nb.net.home \
    --to=kzak@redhat.com \
    --cc=linux-hotplug@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).