Frame Error logs with 'cassis_free_internal addr' & 'matches STRIDE', seen after adding VPLS/irb config.

This is in a Fusion setup where irb or vpls config is on satellite interface.

Below stacktrace info can be seen in logs.

Mar 1 08:30:00 JTAC fpc2 Frame 15: sp = 0x00000000, pc = 0xa5c07d5

Mar 1 08:30:00 JTAC fpc2 Frame 16: sp = 0x00000000, pc = 0x807e75d

Mar 1 08:30:00 JTAC fpc2 Frame 17: sp = 0x00000000, pc = 0xf73ea1a6

Mar 1 08:30:00 JTAC fpc2 cassis_free_internal addr 0xfb76d matches STRIDE, size 2 is bad.

Mar 1 08:30:00 JTAC fpc2 FREE ERR NH[1]: NH, 2 dw (2 blk) @ PA 0xfc37b76d addr 0x37b76d Traceback:

Mar 1 08:30:00 JTAC fpc2 Frame 1: sp = 0x00000000, pc = 0x987f60a

Mar 1 08:30:00 JTAC fpc2 Frame 2: sp = 0x00000000, pc = 0x983b697

Mar 1 08:30:00 JTAC fpc2 Frame 3: sp = 0x00000000, pc = 0x9c76fc9

Mar 1 08:30:00 JTAC fpc2 Frame 4: sp = 0x00000000, pc = 0x9bf2cdf

Mar 1 08:30:00 JTAC fpc2 Frame 5: sp = 0x00000000, pc = 0x9b03392

In NH change scenarios, a platform specific flag for NH's underlying IFL was not getting reset leading to an erroneous attempt to free JNH memory.
Issue was fixed via PR1781132.

There is no functional impact due to these logs.