[Question] Hazard Pointers: is it safe to protect a pointer to invalid memory? about cs431 HOT 5 CLOSED

What the slide is saying that without protection, the access may be unsafe.

Now even if you did protection, the pointer may have been freed between the time you obtained it and called protect(cur). We perform validation to ensure that this does not happen.

from cs431.

Hence we can call protect on an already freed pointer safely? I.e. the protect method doesn't dereference the pointer
Is this: protect(null) also safe then?

from cs431.

protect(null) itself is safe (hence in the homework Shield::protect() is a safe function) what isn't safe is dereference of a null pointer or protected pointer without validation. This is precisely why we validate the pointer and also check if its null.

from cs431.

Okay, so protecting a pointer to invalid memory is safe. Then why does it say "unsafe protect()" on slide 7?

from cs431.

Ah, so the situation in slide 7 is a case where the dereference is unsafe even if validation succeeds. That's why its saying "unsafe protect()".

from cs431.