4,4,4 VXOR IN0, KEY, IN0 // vxor 1,1,3 BDNZ loop128 LVX (PTR)(R0), RCON // lvx 4,0,6 Last two round keys // Key schedule (Round 9) VPERM IN0, IN0, MASK, KEY // vperm 3,1,1,5 Rotate-n-spat VSLDOI $12, ZERO, IN0, TMP // vsldoi 6,0,1,12 STXVD2X IN0, (R0+OUTENC) STXVD2X IN0, (R0+OUTDEC) VCIPHERLAST KEY, RCON, KEY // vcipherlast 3,3,4 ADD $16, OUTENC, OUTENC ADD $-16, OUTDEC, OUTDEC // Key schedule (Round 10) VXOR IN0, TMP, IN0 // vxor 1,1,6 VSLDOI $12, ZERO, TMP, TMP // vsldoi 6,0,6,12 VXOR IN0, TMP, IN0...

4,4,4 VXOR IN0, KEY, IN0 // vxor 1,1,3 BDNZ loop128 LVX (PTR)(R0), RCON // lvx 4,0,6 Last two round keys // Key schedule (Round 9) VPERM IN0, IN0, MASK, KEY // vperm 3,1,1,5 Rotate-n-spat VSLDOI $12, ZERO, IN0, TMP // vsldoi 6,0,1,12 STXVD2X IN0, (R0+OUTENC) STXVD2X IN0, (R0+OUTDEC) VCIPHERLAST KEY, RCON, KEY // vcipherlast 3,3,4 ADD $16, OUTENC, OUTENC ADD $-16, OUTDEC, OUTDEC // Key schedule (Round 10) VXOR IN0, TMP, IN0 // vxor 1,1,6 VSLDOI $12, ZERO, TMP, TMP // vsldoi 6,0,6,12 VXOR IN0, TMP, IN0...

- Truncates a message if it hits the NoteLengthLimit when the scheduler records an event for the pod that indicates the pod has failed to schedule. ([#98715](https://github.com/kubernetes/kubernetes/pull/98715), [@carlory](https://github.com/carlory)) [SIG Scheduling]

* Fixes issue [[#68899](https://github.com/kubernetes/kubernetes/pull/68899)](https://github.com/kubernetes/kubernetes/issues/68899) where pods might schedule on an unschedulable node. ([#68984](https://github.com/kubernetes/kubernetes/pull/68984), [@k82cn](https://github.com/k82cn))

    </magic>
  </mime-type>
  <mime-type type="application/x-mspublisher">
    <glob pattern="*.pub"/>
    <sub-class-of type="application/x-tika-msoffice"/>
  </mime-type>
  <mime-type type="application/x-msschedule">
    <glob pattern="*.scd"/>
  </mime-type>
  <mime-type type="application/x-msterminal">
    <glob pattern="*.trm"/>
  </mime-type>
  <mime-type type="application/x-mswrite">

- Fixed a bug that a pod may remain unscheduled if any PreFilter plugin returns nodes that do not exist. ([#124765](https://github.com/kubernetes/kubernetes/pull/124765), [@chengjoey](https://github.com/chengjoey)) [SIG Scheduling and Testing]

## Dependencies

### Added

- Take the context as the first argument of Schedule. ([#82119](https://github.com/kubernetes/kubernetes/pull/82119), [@wgliang](https://github.com/wgliang))

- Truncates a message if it hits the NoteLengthLimit when the scheduler records an event for the pod that indicates the pod has failed to schedule. ([#98715](https://github.com/kubernetes/kubernetes/pull/98715), [@carlory](https://github.com/carlory)) [SIG Scheduling]

- Kubeadm: during the preflight check "CreateJob" of "kubeadm upgrade", check if there are no nodes where a Pod can schedule. If there are none, show a warning and skip this preflight check. This can happen in single node clusters where the only node was drained. ([#124570](https://github.com/kubernetes/kubernetes/pull/124570), [@neolit123](https://github.com/neolit123))...