IRP_MJ_QUERY_INFORMATION Unsupported File Class Information Type

For an IRP_MJ_QUERY_INFORMATION call (in a File System Driver), if I don’t support one of the FileInformationClass types, what is the error code I’m supposed to return? I swear I’ve seen it somewhere, but I just can’t find it through searching.

I suppose any of these should be fine:
STATUS_NOT_IMPLEMENTED / STATUS_INVALID_INFO_CLASS /
STATUS_INVALID_DEVICE_REQUEST.

Regards,
Ayush Gupta
http://www.linkedin.com/in/guptaayush

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-370206-
xxxxx@lists.osr.com] On Behalf Of xxxxx@seventenstorage.com
Sent: Wednesday, June 17, 2009 7:40 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] IRP_MJ_QUERY_INFORMATION Unsupported File Class
Information Type

For an IRP_MJ_QUERY_INFORMATION call (in a File System Driver), if I
don’t support one of the FileInformationClass types, what is the error
code I’m supposed to return? I swear I’ve seen it somewhere, but I just
can’t find it through searching.


NTFSD is sponsored by OSR

For our schedule of debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Always a good idea to just check the FASTFAT source in cases like this.

-scott


Scott Noone
Consulting Associate
OSR Open Systems Resources, Inc.
http://www.osronline.com

wrote in message news:xxxxx@ntfsd…
> For an IRP_MJ_QUERY_INFORMATION call (in a File System Driver), if I don’t
> support one of the FileInformationClass types, what is the error code I’m
> supposed to return? I swear I’ve seen it somewhere, but I just can’t find
> it through searching.
>

STATUS_INVALID_INFO_CLASS was the one I couldn’t remember.

FASTFAT returns STATUS_INVALID_PARAMETER and it also doesn’t support the same class type we don’t. I’ll experiment with both.

Thank you both.

>>FASTFAT returns STATUS_INVALID_PARAMETER and it also doesn’t support the same class type we don’t. I’ll experiment with both.

I suggest following FastFat instead on any other error code even if the FAT error code does not looks sensible like other available options.

And this is because doing said thing will not raise any sort of errors from applications. I know applications which complain if you fail there call with an error code which is not same as standard FS. In fact I have seen Acrobat complaining during its launch and loading some dll with error, if it do not recieves the exact error code as per its expectation.

So its better to go with standard as they’ll keep *silent* all those app writer who base their code on some return error code.

Thanks
Aditya