glibc-2.23.90-21.fc25 turns the GLIBC_2.24 symbols into compatibility symbols.  This version works as expected, but it has unnecessary compatibility symbols for recvmmsg and sendmmsg on 32-bit architectures (for some reason, these were introduced upstream for recvmsg and sendmsg only).  glibc-2.23.90-22.fc25 removes these unnecessary symbols again, but there is no change in binaries produced or run-time behavior, so both versions are good for building new binaries in preparation of the full ABI change reversal.

glibc-2.23.90-30.fc25 drops the compat symbols.  All affected rawhide packages have been rebuilt.

"All affected rawhide packages have been rebuilt." 

How do we know what are the affected packages ? time range is quite
large 2016-06-11 -> 2016-07-22

(In reply to Sergio Monteiro Basto from comment #3)
> "All affected rawhide packages have been rebuilt." 
> 
> How do we know what are the affected packages ?

I used this query against symboldb:

SELECT source, MAX(build_time)::date build_time,
    json_agg (DISTINCT arch ORDER BY arch) AS architectures
  FROM (SELECT SUBSTRING (p.source FROM '(.*)\.src\.rpm$') AS source, 
            build_time, p.arch
          FROM symboldb.package p
          JOIN symboldb.file USING (package_id)
          JOIN symboldb.elf_reference er USING (contents_id)
          JOIN symboldb.package_set_member USING (package_id)
          WHERE er.name IN ('recvmsg', 'recvmmsg', 'sendmsg', 'sendmmsg')
            AND er.version = 'GLIBC_2.24') x
  GROUP BY source ORDER BY 1;

I applied this against the Koji build roots for i386, x86_64, armhfp, ppc64, ppc64le, s390x, aarch64.