namelookup.c Any BUGS ? memory bugs ?

Hi all and Happy New Year!

Were there any bugs found in the filter
lib(:\WINDDK\3790.1830\src\filesys\filter\lib) namelookup.c source code

Thanks

Daniel.

Get the latest news on SurfControl and our products,
subscribe to our monthly e-newsletter, SurfAdvisory at:
http://www.surfcontrol.com/resources/surfadvisory/surfadvisory_signup.aspx

*********************************************************************
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, distribution or any action taken
or omitted to be taken in reliance on it, is prohibited and may be
unlawful. If you believe that you have received this email in error,
please contact the sender.
*********************************************************************

I have found this in the osr list. no one ever replied to it.

Does any one know if this is a bug? Microsoft team, any comments or
corrections?

FileSpy bug (Microsoft Windows Server 2003 SP1 IFS Development Kit)


Hello, All!

May be it is known, but I don’t found a report about it.

\src\filesys\filter\lib\namelookup.c, line 923:
ASSERT(KeReadStateEvent(&event) ||

!NT_SUCCESS(irp->IoStatus.Status));

It is a bug. The object “irp” can’t be used here it’s freed already (in
the
completion
routine “NLPQueryCompletion”). The bug is affects a debug version of
driver
only.

PS: reported to Microsoft too.

Eugene.


From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Arosh
Sent: Tuesday, January 02, 2007 5:00 PM
To: Windows File Systems Devs Interest List
Subject: [ntfsd] namelookup.c Any BUGS ? memory bugs ?

Hi all and Happy New Year!

Were there any bugs found in the filter
lib(:\WINDDK\3790.1830\src\filesys\filter\lib) namelookup.c source code

Thanks

Daniel.

Get the latest news on SurfControl and our products,
subscribe to our monthly e-newsletter, SurfAdvisory at:
http://www.surfcontrol.com/resources/surfadvisory/surfadvisory_signup.as
px

*********************************************************************
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, distribution or any action taken
or omitted to be taken in reliance on it, is prohibited and may be
unlawful. If you believe that you have received this email in error,
please contact the sender.
*********************************************************************


Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

Hello, Daniel.

The code is fine.
Completion routine always sets event when called, so KeReadStateEvent(&event) returns true and the second expression (!NT_SUCCESS(irp->IoStatus.Status)) not evaluated.

Regards, Dmitry Fleytman

Thank you Dmitry !

Daniel

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
DmitryFleytman@ua.fm
Sent: Wednesday, January 03, 2007 11:20 AM
To: Windows File Systems Devs Interest List
Subject: RE:[ntfsd] namelookup.c Any BUGS ? memory bugs ?

Hello, Daniel.

The code is fine.
Completion routine always sets event when called, so
KeReadStateEvent(&event) returns true and the second expression
(!NT_SUCCESS(irp->IoStatus.Status)) not evaluated.

Regards, Dmitry Fleytman


Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@surfcontrol.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Get the latest news on SurfControl and our products,
subscribe to our monthly e-newsletter, SurfAdvisory at:
http://www.surfcontrol.com/resources/surfadvisory/surfadvisory_signup.aspx

*********************************************************************
The information in this email is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
email by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, distribution or any action taken
or omitted to be taken in reliance on it, is prohibited and may be
unlawful. If you believe that you have received this email in error,
please contact the sender.
*********************************************************************