[Bug nptl/10828] New check added in pthread_attr_setschedparam() causes hard-to-explain behavior

["jdluhos at suse dot cz" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From jdluhos at suse dot cz  2009-10-22 14:16 -------
I agree, LSB tests are often broken.

But in this specific case, I'd say the programmer did nothing wrong. POSIX does
not specify that the pthread_attr structure should be filled in a specific
order, and the EINVAL error in the case of wrong order is hard to explain (the
incorrect priority is not an error *yet*; it would become an error in the moment
of thread creation, but before this, the values in the structure can still be
changed).

Could you please consider this problem once more? If you still have the same
opinion, I will open the bug with LSB - but I'm afraid the same problem can
occur in another codes, as well.

Thank you for your patience.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |


http://sourceware.org/bugzilla/show_bug.cgi?id=10828

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.