This is checking for 8-byte alignment on x86, not 16-byte.
On Sun, Oct 11, 2015 at 2:51 PM, <pschweitzer(a)svn.reactos.org> wrote:
> if (!((ULONG_PTR)Buffers[i] & 0x2))
Best regards,
Alex Ionescu
Hi !
I don't think this commit constitutes a nice improvement for NTVDM at its
present status:
- having the precise list of the used headers in each .c file helped me in
knowing at a glance which functionalities a given .c needed,
- therefore enabling me to find better places where to put the functions and
possibly reduce the number of headers in the future (refactoring).
- This broke my numerous local changes regarding e.g. a modularization of
the CPU layer in NTVDM, video layer, ...
- Finally, stuffing indistinctively *all* the headers (including the private
ones like bios32p.h which purpose was to be used in the sources of one
module only) inside the PCH ntvdm.h, makes for example BIOS or DOS functions
visible inside hardware modules like ps2.h, which is completely illogical
when you try to modularize NTVDM at source level, by completely separating
hardware emulation from bios code and DOS emulation, etc... .
Therefore I will revert your commit tomorrow, while keeping a diff and put
it in a JIRA report.
Cheers,
Hermès.
________________________________________
[ros-diffs] [akhaldi] 69435: [NTVDM] Improve the PCH situation.
akhaldi at svn.reactos.org akhaldi at svn.reactos.org
Sat Oct 3 21:47:46 UTC 2015
Previous message: [ros-diffs] [spetreolle] 69434: [user32_apitest] 0x%lu
does not mean anything correct.
Next message: [ros-diffs] [spetreolle] 69436: [ROSTESTS] Fix 0x%lu
specifier. Add cmake file for notificationtest.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
________________________________________
Author: akhaldi
Date: Sat Oct 3 21:47:46 2015
New Revision: 69435
URL: http://svn.reactos.org/svn/reactos?rev=69435&view=rev
Log:
[NTVDM] Improve the PCH situation.
On 28/09/2015 11:01, sginsberg(a)svn.reactos.org wrote:
> Author: sginsberg
> Date: Mon Sep 28 09:01:11 2015
> New Revision: 69393
>
> URL: http://svn.reactos.org/svn/reactos?rev=69393&view=rev
> Log:
> [NTOS] Fix the Ob wait system calls to only catch the exceptions that are expected to be raised by the Ke wait functions (and not potentially silently catching *any* exception and corrupting everything in the process). Also fixup some code logic. SEH Mega Fixup 1/???
>
> Modified:
> trunk/reactos/ntoskrnl/ob/obwait.c
>
> Modified: trunk/reactos/ntoskrnl/ob/obwait.c
> URL: http://svn.reactos.org/svn/reactos/trunk/reactos/ntoskrnl/ob/obwait.c?rev=6…
> ==============================================================================
> --- trunk/reactos/ntoskrnl/ob/obwait.c [iso-8859-1] (original)
> +++ trunk/reactos/ntoskrnl/ob/obwait.c [iso-8859-1] Mon Sep 28 09:01:11 2015
> @@ -49,12 +49,12 @@
> IN BOOLEAN Alertable,
> IN PLARGE_INTEGER TimeOut OPTIONAL)
> {
> - PKWAIT_BLOCK WaitBlockArray = NULL;
> + PKWAIT_BLOCK WaitBlockArray;
> HANDLE Handles[MAXIMUM_WAIT_OBJECTS], KernelHandle;
> PVOID Objects[MAXIMUM_WAIT_OBJECTS];
> PVOID WaitObjects[MAXIMUM_WAIT_OBJECTS];
> - ULONG i = 0, ReferencedObjects = 0, j;
> - KPROCESSOR_MODE PreviousMode = ExGetPreviousMode();
> + ULONG i, ReferencedObjects, j;
> + KPROCESSOR_MODE PreviousMode;
> LARGE_INTEGER SafeTimeOut;
> BOOLEAN LockInUse;
> PHANDLE_TABLE_ENTRY HandleEntry;
> @@ -65,31 +65,26 @@
> NTSTATUS Status;
> PAGED_CODE();
>
> - /* Enter a critical region since we'll play with handles */
> - LockInUse = TRUE;
> - KeEnterCriticalRegion();
> -
> /* Check for valid Object Count */
> if ((ObjectCount > MAXIMUM_WAIT_OBJECTS) || !(ObjectCount))
> {
> /* Fail */
> - Status = STATUS_INVALID_PARAMETER_1;
> - goto Quickie;
> + return STATUS_INVALID_PARAMETER_1;
> }
>
> /* Check for valid Wait Type */
> if ((WaitType != WaitAll) && (WaitType != WaitAny))
> {
> /* Fail */
> - Status = STATUS_INVALID_PARAMETER_3;
> - goto Quickie;
> - }
> -
> - /* Enter SEH */
> - _SEH2_TRY
> - {
> - /* Check if the call came from user mode */
> - if (PreviousMode != KernelMode)
> + return STATUS_INVALID_PARAMETER_3;
> + }
> +
> + /* Enter SEH for user mode */
> + PreviousMode = ExGetPreviousMode();
> + if (PreviousMode != KernelMode)
> + {
> + /* Enter SEH */
> + _SEH2_TRY
No, this is plain wrong.
This is not because you're in kernel mode that the world is marvelous
and callers trustable.
A caller can pass you buggy address and you HAVE to wrap the
RtlCopyMemory in SEH to make sure that if a buggy address is passed, the
whole system isn't brought down (that's the whole purpose of the copy
after all!).
In case you have a doubt, just put some random:
Status = ZwWaitForMultipleObjects(2, (void **)0x42424242, WaitAll,
FALSE, NULL);
In a kernel component. In w2k3, you'll get Status = STATUS_ACCESS_VIOLATION
In ReactOS, with your changes: BSOD.
Please before doing random changes that you believe are right: do testing.
Alex already told you that.
Cheers,
--
Pierre Schweitzer <pierre at reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
Hello,
Let me invite you to the monthly status meeting taking place last
Thursday of a month, 24th of September, 19:00 UTC, as usual.
IRC service will only be started shortly before the meeting. Your
participation passwords and server address will be emailed to you
shortly before the meeting starts, and they are going to be different
once again as they are not stored in any database. Hopefully it's not
much of inconvenience.
Please send agenda proposals to me before the meeting.
Regards,
Aleksey Bragin