Email List: Xaustin-review-lX
[All Lists]

Defect in XSH 2.8.3.1 Memory Locking

To: yyyyyyyyyyyyyyy@xxxxxxxxxxxxx
Subject: Defect in XSH 2.8.3.1 Memory Locking
From: yyyyyyy@xxxxxxxxxx
Date: Wed, 20 Mar 2002 06:28:21 GMT
        Defect report from : Ulrich Drepper , Red Hat, Inc.

(Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)

@ page 43 line 1759-1770 section 2.8.3.1 Memory Locking objection {ud-13}

Problem:

Defect code :  1. Error

The first paragraph of section 2.8.3.1 says that the functionality
described in the section is only available if the Process Memory Locking
option is available.  This is not true.

The second paragraph describes functionality which is only available if
the Range Memory Locking option is available.  There is nowhere any
wording which requires that Process Memory Locking must be available if
Range Memory Locking is available.

So there are two problems:

- the first paragraph must say that the section applies also for Range
  Memory Locking

- the second paragraph only applies for Range Memory Locking


Action:

The way the first paragraph is used becomes cumbersome with the
necessary change therefore the proposed change is this:

- remove the first paragraph explaining the missing shading

- shade the second paragraph and mark it MLR

- shade the third paragraph and mark it ML|MLR

<Prev in Thread] Current Thread [Next in Thread>
  • Defect in XSH 2.8.3.1 Memory Locking, drepper <=