On 11-10-18 11:30, NeilBrown wrote:

On Tue, 18 Oct 2011 10:16:41 +0100 "Orlowski, Lukasz"
[off-list ref]  wrote:

quoted

Hi,

I was going through mdadm code and got to realize that r/w
operations are invoked without TEMP_FAILURE_RETRY() macro, which
protects from unexpected operation termination, case SIGINT is
thrown. According to my knowledge its POSIX best-practice to call
the r/w operations within that macro, lest some sporadic unexpected
behaviors occur.

Any particular reason for not using it?

I've never heard of TEMP_FAILURE_RETRY.

And having looked in to it I would certainly try to avoid using it.

As this grabbed my attention ..

that macro is just a shortcut to something along the:

do {
	ret = read/write/etc.( ... );
} while (ret < 0 && errno == EINTR);

which has always been the proper way to handle such situations 
(recollecting Stevens books, glibc reference manual, or any other solid 
source). Why avoid using it ? Costs nothing, and guarantees we won't run 
into some corner case.

If the SA_RESTART flag is set with sigaction() then it should be
totally unnecessary.

signals(7) has pretty large list of when it can or cannot happen, and
when it will always happen regardless of SA_RESTART. And it would be 
quite different list when other unix vendors are considered (which 
doesn't of course apply to mdadm case, it being only linux specific). 
There're also not ignorable stop signals (and under some cases they will 
end with EINTR as well).

And it's not only SIGINT (as the original mail could suggest), any not 
ignored signal can cause it.