)]}'
{
  "commit": "3daad7f60aa92d0307fa2b2edd38c886a09902f2",
  "tree": "f9bcef51328a8cb995cd05748308fa20d2006c5c",
  "parents": [
    "539b7cf1f77a5135241f410777b3c780c6e23994"
  ],
  "author": {
    "name": "Jan Polensky",
    "email": "japo@linux.ibm.com",
    "time": "Thu May 21 14:01:32 2026 +0200"
  },
  "committer": {
    "name": "Alexander Gordeev",
    "email": "agordeev@linux.ibm.com",
    "time": "Thu May 28 12:08:27 2026 +0200"
  },
  "message": "s390/bug: Always emit format word in __BUG_ENTRY\n\nWhen CONFIG_DEBUG_BUGVERBOSE is disabled, the s390 __BUG_ENTRY() macro\nomits the format string pointer, so the generated __bug_table entry no\nlonger matches struct bug_entry.\n\nWith HAVE_ARCH_BUG_FORMAT enabled, the generic BUG infrastructure reads\nbug_entry::format via bug_get_format(). If the format word is missing,\nsubsequent fields are read from the wrong offset, which may:\n- Misinterpret flags (BUG vs WARN classification errors)\n- Fault when dereferencing a misread format pointer\n\nThe root cause is that __BUG_ENTRY() delegates format word emission to\n__BUG_ENTRY_VERBOSE(), which is conditional on CONFIG_DEBUG_BUGVERBOSE.\n\nFix this by moving the format field emission directly into __BUG_ENTRY()\nso it is always emitted unconditionally. Remove the format parameter from\n__BUG_ENTRY_VERBOSE() and keep only file/line emission conditional on\nCONFIG_DEBUG_BUGVERBOSE.\n\nFixes: 2b71b8ab9718 (\"s390/bug: Use BUG_FORMAT for DEBUG_BUGVERBOSE_DETAILED\")\nSigned-off-by: Jan Polensky \u003cjapo@linux.ibm.com\u003e\nReviewed-by: Heiko Carstens \u003chca@linux.ibm.com\u003e\nSigned-off-by: Alexander Gordeev \u003cagordeev@linux.ibm.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "59017fd3d9358d495fc06ec9775b12cbb4c27f37",
      "old_mode": 33188,
      "old_path": "arch/s390/include/asm/bug.h",
      "new_id": "50a270edb020350065beefa5de2964435b710d6b",
      "new_mode": 33188,
      "new_path": "arch/s390/include/asm/bug.h"
    }
  ]
}
