IBM Support

IV88366: FUSER/PROCFILES COMMAND MAY STUCK IN AN ENDLESS LOOP APPLIES TO AIX 7100-03 17/01/27 PTF PECHANGE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The fuser command may stuck in an endless loop.
    Using truss -p <fuser PID> will show that fuser
    is working on the same files over and over again.
    Example:
    getdirent(3, 0x000000012BD1E890, 1024) = 816
    <snip>
    statx("/proc/10223694/fd/106",...)
    statfs("/proc/10223694/fd/106",...)
    statx("/proc/10223694/fd/109",...)
    statfs("/proc/10223694/fd/109",...)
    getdirent(3, 0x000000012BD1E890, 1024) = 1008
    statx("/proc/10223694/fd/0",...)
    statfs("/proc/10223694/fd/0",...)
    statx("/proc/10223694/fd/1",...)
    statfs("/proc/10223694/fd/1",...)
    <snap>
    statx("/proc/10223694/fd/106",...)
    statfs("/proc/10223694/fd/106",...)
    statx("/proc/10223694/fd/109",...)
    statfs("/proc/10223694/fd/109",...)
    getdirent(3, 0x000000012BD1E890, 1024) = 1008
    statx("/proc/10223694/fd/0",...)
    <snip>
    In this case the command
    procfiles 10223694
    will loop as well.
    

Local fix

  • For the fuser command:
    export FUSER_VERSION=1
    run the command/script executing fuser
    unset FUSER_VERSION
    No workaround for procfiles.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:
    * Systems running the 7100-03 Technology Level with
    * bos.mp64 at or between 7.1.3.15 and 7.1.3.48
    ****************************************************************
    * PROBLEM DESCRIPTION:
    * The fuser command may stuck in an endless loop.
    * Using truss -p <fuser PID> will show that fuser
    * is working on the same files over and over again.
    * Example:
    * getdirent(3, 0x000000012BD1E890, 1024) = 816
    * <snip>
    * statx("/proc/10223694/fd/106",...)
    * statfs("/proc/10223694/fd/106",...)
    * statx("/proc/10223694/fd/109",...)
    * statfs("/proc/10223694/fd/109",...)
    * getdirent(3, 0x000000012BD1E890, 1024) = 1008
    * statx("/proc/10223694/fd/0",...)
    * statfs("/proc/10223694/fd/0",...)
    * statx("/proc/10223694/fd/1",...)
    * statfs("/proc/10223694/fd/1",...)
    * <snap>
    * statx("/proc/10223694/fd/106",...)
    * statfs("/proc/10223694/fd/106",...)
    * statx("/proc/10223694/fd/109",...)
    * statfs("/proc/10223694/fd/109",...)
    * getdirent(3, 0x000000012BD1E890, 1024) = 1008
    * statx("/proc/10223694/fd/0",...)
    * <snip>
    * In this case the command
    * procfiles 10223694
    * will loop as well.
    ****************************************************************
    * RECOMMENDATION:
    * Install APAR IV88366.
    ****************************************************************
    

Problem conclusion

  • offset caluclation is changed  in such a way that it is
    dependent on the last filename that was returned.
    

Temporary fix

Comments

  • 6100-09 - use AIX APAR IV74403
    7100-04 - use AIX APAR IV73971
    

APAR Information

  • APAR number

    IV88366

  • Reported component name

    AIX V7.1

  • Reported component ID

    5765H4000

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-19

  • Closed date

    2016-08-19

  • Last modified date

    2017-01-27

  • APAR is sysrouted FROM one or more of the following:

    IV73971

  • APAR is sysrouted TO one or more of the following:

    002PC0Ÿ

Fix information

  • Fixed component name

    AIX V7.1

  • Fixed component ID

    5765H4000

Applicable component levels

  • R710 PSY U872346

       UP17/01/19 I 1000

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SG11R"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]

Document Information

Modified date:
20 April 2022