public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug nss/30151] New: sgetsgent_r does not implement ERANGE protocol compatible with sgetsgent
@ 2023-02-21  8:13 fweimer at redhat dot com
  2023-02-21  8:13 ` [Bug nss/30151] " fweimer at redhat dot com
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: fweimer at redhat dot com @ 2023-02-21  8:13 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=30151

            Bug ID: 30151
           Summary: sgetsgent_r does not implement ERANGE protocol
                    compatible with sgetsgent
           Product: glibc
           Version: 2.38
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nss
          Assignee: unassigned at sourceware dot org
          Reporter: fweimer at redhat dot com
  Target Milestone: ---

The sgetsgent function checks errno for ERANGE, but sgetsgent_r only returns
ERANGE, but does not set errno to ERANGE. As a result, sgetsgent does not
detect failure at all, and returns indicating success without filling in the
struct sgrp result.

This bug is somewhat similar in effect as bug 20338, but the root cause is
quite different.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2023-02-23 15:23 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-21  8:13 [Bug nss/30151] New: sgetsgent_r does not implement ERANGE protocol compatible with sgetsgent fweimer at redhat dot com
2023-02-21  8:13 ` [Bug nss/30151] " fweimer at redhat dot com
2023-02-21  8:13 ` fweimer at redhat dot com
2023-02-21  8:42 ` fweimer at redhat dot com
2023-02-21  8:53 ` sam at gentoo dot org
2023-02-22  7:16 ` sam at gentoo dot org
2023-02-23 15:23 ` fweimer at redhat dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).