July 2012 - Darwin-kernel - lists.apple.com

Re: About partition scheme.
by Phil Jordan 06 Jul '12

06 Jul '12

On Thu, Jul 5, 2012 at 4:25 AM, Flost.D.Li <havefan2012(a)gmail.com> wrote: >> The driver matches on the special partition type with the GUID, in >> this case, disk2s2, and creates a "whole" IOMedia object, in this case >> disk3. > > [Flost] so the disk3 was generated by disk2s2. The provider for my driver is the IOMedia for disk2s2 (it actually can and usually does have more than one provider, but that's irrelevant here), and the IOMedia nub my driver generates is disk3. > Can you control the inter activation with disk2s2? What do you mean by that? >> https://developer.apple.com/library/mac/#documentation/Darwin/Conceptual/KE… > [Flost]: Yes, I'd read this document before, but last time when i have two machine to study this, I find that only the system got panic, than the debug machine could connect to the test machine, and show the stack, but this does not make much help than I use the panic file to decode the stack. > May be I could read the article more carefully. Also, I will reference the following article to learn about firewire kprintf. You can do most things that you can do with user-space gdb. You might also want to look at all the macros in kgmacros. Some of those are extremely useful. If you want to force your code to break to the debugger (e.g. in your own replacement for assert()), use __asm__("int $3"); (at least on i386/x86-64) phil _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: About partition scheme.
by Phil Jordan 06 Jul '12

06 Jul '12

On Thu, Jul 5, 2012 at 4:13 AM, Sid Moore <learnmost(a)gmail.com> wrote: > Yes, Phil's analysis is able to exactly depict this panic. I think > What Flost need is that his own driver class can take over the whole > disk and all the request to his disks should pass through his driver > code. So, I guess his own driver class should inherit from > IOBlockStorageDevice and make IOBlockStorageDriver as its provider? > Am I correct? Hmm. I don't know, that seems like it's asking for trouble. Is there a good reason not to go through the IOMedia? phil _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Is Darwin 11.4.0 capable of NFSv4?
by Mike Mackovitch 05 Jul '12

05 Jul '12

On Thu, Jul 05, 2012 at 10:22:03AM +0800, Sid Moore wrote: > On Mon, Jul 2, 2012 at 11:20 PM, Andreas Boesen <andreasb(a)selfnet.de> wrote: > > Hi, > > > > does OS X 10.7 support NFSv4 as a client. I couldn't find any documentation > > on developer.apple.com or Googol. > > > > There is only the man-Page[1] and a thread in this list[2] indicating that > > OS X 10.6 as NFSv4.0alpha support. > > > > Could someone point me to some kind of "changelog" or Documentation about > > the status of the NFS client implementation in OS X 10.7 please? Here's a documentation link: > > [1] http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManP… Note that the "vers=4.0alpha" mentioned in the 10.6 version of the man page is no longer supported and that "vers=4" is now supported in 10.7. That would indicate that the NFSv4 support is no longer considered "alpha" quality. > It seems that AFP is the default NAS protocol in MacOSX, rather than > NFS. And I also think NFS implementation in XNU kernel is too old and > related bugs can't be fixed ASAP. But I also want to know why > NFSv4(4.0/4.1, pNFS included) is not supported on MacOSX. Because customers aren't asking for it. HTH --macko _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: About partition scheme.
by Flost.D.Li 05 Jul '12

05 Jul '12

THanks phil, 在 2012-7-4，下午9:24， Phil Jordan 写道： > On Wed, Jul 4, 2012 at 2:54 PM, Li Flost.Dexiong <havefan2012(a)gmail.com> wrote: >> >> 在 2012-7-4，下午8:34， Phil Jordan 写道： >> >>> On Wed, Jul 4, 2012 at 2:17 PM, Li Flost.Dexiong <havefan2012(a)gmail.com> wrote: >>>> [Flost]: I had once try to init my newMedia using true as the "isWhole" argument. but this will cause the system panic. >>> >>> I've successfully written drivers which pass true for the isWhole >>> argument. It works. >> [Flost] Does your device match your driver still show that #0 and #1 on one disk? > > My driver actually matches on a specific partition type, so it looks > something like this (disk2 is the "real" disk): > > /dev/disk2 > #: TYPE NAME SIZE IDENTIFIER > 0: GUID_partition_scheme *160.0 GB disk2 > 1: EFI 209.7 MB disk2s1 > 2: E2A2381C-BE82-4CA7-B0D4-1B9F99BC285D 143.2 GB disk2s2 > 3: Apple_Boot Booter 268.4 MB disk2s3 > > /dev/disk3 > #: TYPE NAME SIZE IDENTIFIER > 0: Apple_HFS Lion *143.2 GB disk3 > > The driver matches on the special partition type with the GUID, in > this case, disk2s2, and creates a "whole" IOMedia object, in this case > disk3. [Flost] so the disk3 was generated by disk2s2. Can you control the inter activation with disk2s2? > > There's nothing stopping you from matching on a whole disk (disk2) AND > creating a whole disk (disk3). Normally, in your probe() and start() > you would read a small piece of data from the start or end of the > provider, and check that a special signature is present, to make sure > this really is a disk that belongs to your driver. The child IOMedia > device would then be slightly smaller than the provider and not cover > that signature. That way, when matching happens for your new media > device (disk3), although your probe() will be called again for this > new device, it can't find the signature and probe() will fail. This > then lets other drivers carry on matching. > > Examples of this are all the usual partition schemes: if you create > only one partition with the maximum possible size, it won't cover the > whole disk, but instead be slightly smaller, as the rest of the space > is taken up by the partition table. > >>> The panic probably doesn't happen on line 565 itself. I suggest using >>> 2-machine debugging and synchronous kprintf logging. It really helps. >> [Flost]: Does this 2-mahines debugging method enable a runtime debugging? >> If yes, what can I refer to? > > Yes, it's not quite as powerful as user-space debugging, but you can > set breakpoints, inspect data, etc. It's briefly explained here: > > https://developer.apple.com/library/mac/#documentation/Darwin/Conceptual/KE… [Flost]: Yes, I'd read this document before, but last time when i have two machine to study this, I find that only the system got panic, than the debug machine could connect to the test machine, and show the stack, but this does not make much help than I use the panic file to decode the stack. May be I could read the article more carefully. Also, I will reference the following article to learn about firewire kprintf. > > You can find more details on it elsewhere on the web and in OSX kernel > books, and in the archives of this mailing list. > > > For firewire or serial port kprintf, set the relevant bit in the debug > setting of the kernel's boot-args: > http://developer.apple.com/library/mac/#documentation/Darwin/Conceptual/Ker… > > For firewire kprintf, run the fwkpfv terminal utility on the other > machine (the other machine must not be using the firewire port for > anything other than kernel debugging). I usually give it a big buffer, > e.g. fwkpfv --buffer=5000000 to avoid overruns. > > For serial port kprintf (only works on old XServes with a serial port, > or virtual machines with a virtual serial port) you just log the raw > data on the other side of the serial cable. > >>> You can't just "get rid of" disk1 as that's not generated in your >>> code, and is in fact the provider to your filter scheme. You NEED it >>> to exist. >> [Flost]: yes, I'd think about this before. but a saw that the disk labeled by Xsan was shown as below: >> /dev/disk9 >> #: TYPE NAME SIZE IDENTIFIER >> 0: Apple_Xsan_Component *5.4 GB disk9 >> >> It didn't show the two # . how does this to be understood? > > I don't know where the Xsan stuff is coming from, but this is > basically an unpartitioned, whole disk (disk9). > > phil Best regards, Flost.D.Li havefan2012(a)gmail.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Is Darwin 11.4.0 capable of NFSv4?
by Sid Moore 05 Jul '12

05 Jul '12

On Mon, Jul 2, 2012 at 11:20 PM, Andreas Boesen <andreasb(a)selfnet.de> wrote: > Hi, > > does OS X 10.7 support NFSv4 as a client. I couldn't find any documentation > on developer.apple.com or Googol. > > There is only the man-Page[1] and a thread in this list[2] indicating that > OS X 10.6 as NFSv4.0alpha support. > > Could someone point me to some kind of "changelog" or Documentation about > the status of the NFS client implementation in OS X 10.7 please? > > Thanks > Andreas > > > > [1] > http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManP… > [2] http://lists.apple.com/archives/darwin-kernel/2009/Aug/msg00048.html > It seems that AFP is the default NAS protocol in MacOSX, rather than NFS. And I also think NFS implementation in XNU kernel is too old and related bugs can't be fixed ASAP. But I also want to know why NFSv4(4.0/4.1, pNFS included) is not supported on MacOSX. > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/darwin-kernel/learnmost%40gmail.com > > This email sent to learnmost(a)gmail.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: About partition scheme.
by Sid Moore 05 Jul '12

05 Jul '12

On Wed, Jul 4, 2012 at 8:34 PM, Phil Jordan <lists(a)philjordan.eu> wrote: > On Wed, Jul 4, 2012 at 2:17 PM, Li Flost.Dexiong <havefan2012(a)gmail.com> wrote: >> [Flost]: I had once try to init my newMedia using true as the "isWhole" argument. but this will cause the system panic. > > I've successfully written drivers which pass true for the isWhole > argument. It works. Your panic is probably caused by multiple > instances of your partition scheme stacking on top of each other: > > - disk1 is inserted and starts matching > - your partition scheme matches on disk1 > - the condition in your probe() is fulfilled by disk1 > - your partition scheme start()s and creates a new "whole" IOMedia object, disk2 > - disk2 appears and starts matching > - your partition scheme matches on disk2 > - the condition in your probe() is fulfilled by disk2 > - your partition scheme start()s and creates a new "whole" IOMedia object, disk3 > > etc. etc. > > Until you run out of some resource. Yes, Phil's analysis is able to exactly depict this panic. I think What Flost need is that his own driver class can take over the whole disk and all the request to his disks should pass through his driver code. So, I guess his own driver class should inherit from IOBlockStorageDevice and make IOBlockStorageDriver as its provider? Am I correct? > > Basically, your probe() shouldn't succeed for disk2, but it does. > That's where your bug is (one of them anyway). > >> on line 565, if i set the false to true, the system got panic when my disk was insert into the system. > > The panic probably doesn't happen on line 565 itself. I suggest using > 2-machine debugging and synchronous kprintf logging. It really helps. > >> or some way to prevent the #0 to be created? > > Let's assume the disk you are inserting is a USB stick. When you > insert it, the USB storage driver creates a new storage object, which > generates a IOMedia object named "disk1". This is the "#0" you are > seeing. Your driver hasn't even loaded at this point. When your filter > scheme matches on disk1, you have 2 options for creating IOMedia > objects: > > isWhole = true: your IOMedia objects will be named "disk2", "disk3", > etc. and look like "whole" physical devices. > isWhole = false: your IOMedia objects will be named "disk1s1", > "disk1s2", etc. and look like partitions. > > You can't just "get rid of" disk1 as that's not generated in your > code, and is in fact the provider to your filter scheme. You NEED it > to exist. > > HTH > phil > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/darwin-kernel/learnmost%40gmail.com > > This email sent to learnmost(a)gmail.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: About partition scheme.
by Phil Jordan 04 Jul '12

04 Jul '12

On Wed, Jul 4, 2012 at 2:54 PM, Li Flost.Dexiong <havefan2012(a)gmail.com> wrote: > > 在 2012-7-4，下午8:34， Phil Jordan 写道： > >> On Wed, Jul 4, 2012 at 2:17 PM, Li Flost.Dexiong <havefan2012(a)gmail.com> wrote: >>> [Flost]: I had once try to init my newMedia using true as the "isWhole" argument. but this will cause the system panic. >> >> I've successfully written drivers which pass true for the isWhole >> argument. It works. > [Flost] Does your device match your driver still show that #0 and #1 on one disk? My driver actually matches on a specific partition type, so it looks something like this (disk2 is the "real" disk): /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *160.0 GB disk2 1: EFI 209.7 MB disk2s1 2: E2A2381C-BE82-4CA7-B0D4-1B9F99BC285D 143.2 GB disk2s2 3: Apple_Boot Booter 268.4 MB disk2s3 /dev/disk3 #: TYPE NAME SIZE IDENTIFIER 0: Apple_HFS Lion *143.2 GB disk3 The driver matches on the special partition type with the GUID, in this case, disk2s2, and creates a "whole" IOMedia object, in this case disk3. There's nothing stopping you from matching on a whole disk (disk2) AND creating a whole disk (disk3). Normally, in your probe() and start() you would read a small piece of data from the start or end of the provider, and check that a special signature is present, to make sure this really is a disk that belongs to your driver. The child IOMedia device would then be slightly smaller than the provider and not cover that signature. That way, when matching happens for your new media device (disk3), although your probe() will be called again for this new device, it can't find the signature and probe() will fail. This then lets other drivers carry on matching. Examples of this are all the usual partition schemes: if you create only one partition with the maximum possible size, it won't cover the whole disk, but instead be slightly smaller, as the rest of the space is taken up by the partition table. >> The panic probably doesn't happen on line 565 itself. I suggest using >> 2-machine debugging and synchronous kprintf logging. It really helps. > [Flost]: Does this 2-mahines debugging method enable a runtime debugging? > If yes, what can I refer to? Yes, it's not quite as powerful as user-space debugging, but you can set breakpoints, inspect data, etc. It's briefly explained here: https://developer.apple.com/library/mac/#documentation/Darwin/Conceptual/KE… You can find more details on it elsewhere on the web and in OSX kernel books, and in the archives of this mailing list. For firewire or serial port kprintf, set the relevant bit in the debug setting of the kernel's boot-args: http://developer.apple.com/library/mac/#documentation/Darwin/Conceptual/Ker… For firewire kprintf, run the fwkpfv terminal utility on the other machine (the other machine must not be using the firewire port for anything other than kernel debugging). I usually give it a big buffer, e.g. fwkpfv --buffer=5000000 to avoid overruns. For serial port kprintf (only works on old XServes with a serial port, or virtual machines with a virtual serial port) you just log the raw data on the other side of the serial cable. >> You can't just "get rid of" disk1 as that's not generated in your >> code, and is in fact the provider to your filter scheme. You NEED it >> to exist. > [Flost]: yes, I'd think about this before. but a saw that the disk labeled by Xsan was shown as below: > /dev/disk9 > #: TYPE NAME SIZE IDENTIFIER > 0: Apple_Xsan_Component *5.4 GB disk9 > > It didn't show the two # . how does this to be understood? I don't know where the Xsan stuff is coming from, but this is basically an unpartitioned, whole disk (disk9). phil _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: About partition scheme.
by Li Flost.Dexiong 04 Jul '12

04 Jul '12

在 2012-7-4，下午8:34， Phil Jordan 写道： > On Wed, Jul 4, 2012 at 2:17 PM, Li Flost.Dexiong <havefan2012(a)gmail.com> wrote: >> [Flost]: I had once try to init my newMedia using true as the "isWhole" argument. but this will cause the system panic. > > I've successfully written drivers which pass true for the isWhole > argument. It works. [Flost] Does your device match your driver still show that #0 and #1 on one disk? > Your panic is probably caused by multiple > instances of your partition scheme stacking on top of each other: > > - disk1 is inserted and starts matching > - your partition scheme matches on disk1 > - the condition in your probe() is fulfilled by disk1 > - your partition scheme start()s and creates a new "whole" IOMedia object, disk2 > - disk2 appears and starts matching > - your partition scheme matches on disk2 > - the condition in your probe() is fulfilled by disk2 > - your partition scheme start()s and creates a new "whole" IOMedia object, disk3 > > etc. etc. > > Until you run out of some resource. > > Basically, your probe() shouldn't succeed for disk2, but it does. > That's where your bug is (one of them anyway). > >> on line 565, if i set the false to true, the system got panic when my disk was insert into the system. > > The panic probably doesn't happen on line 565 itself. I suggest using > 2-machine debugging and synchronous kprintf logging. It really helps. [Flost]: Does this 2-mahines debugging method enable a runtime debugging? If yes, what can I refer to? > >> or some way to prevent the #0 to be created? > > Let's assume the disk you are inserting is a USB stick. When you > insert it, the USB storage driver creates a new storage object, which > generates a IOMedia object named "disk1". This is the "#0" you are > seeing. Your driver hasn't even loaded at this point. When your filter > scheme matches on disk1, you have 2 options for creating IOMedia > objects: > > isWhole = true: your IOMedia objects will be named "disk2", "disk3", > etc. and look like "whole" physical devices. > isWhole = false: your IOMedia objects will be named "disk1s1", > "disk1s2", etc. and look like partitions. > > You can't just "get rid of" disk1 as that's not generated in your > code, and is in fact the provider to your filter scheme. You NEED it > to exist. [Flost]: yes, I'd think about this before. but a saw that the disk labeled by Xsan was shown as below: /dev/disk9 #: TYPE NAME SIZE IDENTIFIER 0: Apple_Xsan_Component *5.4 GB disk9 It didn't show the two # . how does this to be understood? > > HTH > phil Best regards, Flost.D.Li havefan2012(a)gmail.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: About partition scheme.
by Phil Jordan 04 Jul '12

04 Jul '12

On Wed, Jul 4, 2012 at 2:17 PM, Li Flost.Dexiong <havefan2012(a)gmail.com> wrote: > [Flost]: I had once try to init my newMedia using true as the "isWhole" argument. but this will cause the system panic. I've successfully written drivers which pass true for the isWhole argument. It works. Your panic is probably caused by multiple instances of your partition scheme stacking on top of each other: - disk1 is inserted and starts matching - your partition scheme matches on disk1 - the condition in your probe() is fulfilled by disk1 - your partition scheme start()s and creates a new "whole" IOMedia object, disk2 - disk2 appears and starts matching - your partition scheme matches on disk2 - the condition in your probe() is fulfilled by disk2 - your partition scheme start()s and creates a new "whole" IOMedia object, disk3 etc. etc. Until you run out of some resource. Basically, your probe() shouldn't succeed for disk2, but it does. That's where your bug is (one of them anyway). > on line 565, if i set the false to true, the system got panic when my disk was insert into the system. The panic probably doesn't happen on line 565 itself. I suggest using 2-machine debugging and synchronous kprintf logging. It really helps. > or some way to prevent the #0 to be created? Let's assume the disk you are inserting is a USB stick. When you insert it, the USB storage driver creates a new storage object, which generates a IOMedia object named "disk1". This is the "#0" you are seeing. Your driver hasn't even loaded at this point. When your filter scheme matches on disk1, you have 2 options for creating IOMedia objects: isWhole = true: your IOMedia objects will be named "disk2", "disk3", etc. and look like "whole" physical devices. isWhole = false: your IOMedia objects will be named "disk1s1", "disk1s2", etc. and look like partitions. You can't just "get rid of" disk1 as that's not generated in your code, and is in fact the provider to your filter scheme. You NEED it to exist. HTH phil _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: About partition scheme.
by Li Flost.Dexiong 04 Jul '12

04 Jul '12

Hi Phil, Thanks for your response. please see my comment below 在 2012-7-4，下午7:45， Phil Jordan 写道： > On Wed, Jul 4, 2012 at 8:14 AM, Li Flost.Dexiong <havefan2012(a)gmail.com> wrote: >> /dev/disk1 >> #: TYPE NAME SIZE IDENTIFIER >> 0: *16.1 GB disk1 >> 1: new_testdisk 16.1 GB disk1s1 >> >> >> I'm wandering why there is a #0 on my disk, when and how does it create? > > "disk 0" is the whole disk that the partition scheme sits inside. Look > at the IOMedia hierarchy in IORegistryExplorer and it'll make more > sense. > >> Also, are there any reference about how the "disk1s1" string was generate and record on my system? > > The "1" is generated from the location you set on your newly created > IOMedia object like so: > newMedia->setLocation("1"); > This only happens if the IOMedia object isn't "whole". If it's whole, > a new diskX node is generated. [Flost]: I had once try to init my newMedia using true as the "isWhole" argument. but this will cause the system panic. my init of this media call was(this will not panic. but the #0 was created.): 8 #define UUIDLEN 16 9 typedef struct mydisk{ 10 UInt32 DISKTYPE; 11 UInt32 headerlength; 12 UInt32 checksum; 13 UInt32 version; 14 UInt64 vollength; 15 unsigned char uuid[UUIDLEN]; 16 }__attribute__((packed)) mydisk_t; 552 IOMedia * My_Scheme::instantiateMediaObject(mydisk_t* partition) 553 { 554 IOMedia *media = getProvider(); 555 UInt64 mediaBlockSize = media->getPreferredBlockSize(); 556 IOMedia *newMedia; 557 558 newMedia = new IOMedia; 559 if (newMedia) { 560 UInt64 partionBase, partionSize; 561 partionBase = 0; //OSSwapLittleToHostInt64(partition->base) * mediaBlockSize; 562 partionSize = partition->vollength; //OSSwapLittleToHostInt64(partition->size) * mediaBlockSize; 563 564 if (newMedia->init(partionBase, partionSize, mediaBlockSize, media->getAttributes(),\ 565 false, media->isWritable(), "new_testdisk")) { 566 newMedia->setName("new_testdisk"); 567 char location[12]; 568 uuid_string_t uuid; 569 uuid_unparse(partition->uuid, uuid); 570 snprintf(location, sizeof(location), "%d", devcnt); 571 newMedia->setProperty(kIOMediaPartitionIDKey, devcnt, 32); 572 newMedia->setLocation(location); 573 newMedia->setProperty(kIOMediaUUIDKey, uuid); 574 } else { 575 newMedia->release(); 576 newMedia = NULL; 577 } 578 } 579 return newMedia; 580 } on line 565, if i set the false to true, the system got panic when my disk was insert into the system. the mydisk_t was write the the disk before hand. and read in probe() function. and make the bit-order swap when read. this InstantiateMediaObject was call by start function. Is there any property that i could set this media is a whole? or some way to prevent the #0 to be created? > > HTH > phil Best regards, Flost.D.Li havefan2012(a)gmail.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0