[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191007082541.64146933.7@infradead.org>
Date: Mon, 07 Oct 2019 10:25:41 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: x86@...nel.org
Cc: peterz@...radead.org, linux-kernel@...r.kernel.org,
rostedt@...dmis.org, mhiramat@...nel.org, bristot@...hat.com,
jbaron@...mai.com, torvalds@...ux-foundation.org,
tglx@...utronix.de, mingo@...nel.org, namit@...are.com,
hpa@...or.com, luto@...nel.org, ard.biesheuvel@...aro.org,
jpoimboe@...hat.com
Subject: [PATCH v2 0/4] Propagate module notifier errors
These patches came from the desire to propagate MODULE_STATE_COMING errors.
While looking at that I spotted fail with a number of module notifiers
themselves and with the whole notification business.
I will probably add a notifier for MODULE_STATE_UNFORMED, but that is later.
Fixing this error propagation fixes a fairly serious (but really uncommon) bug
when memory allocation fails for jump-labels while loading a module. And since
we're going to be introducing more of that (static_call), fix it now.
Powered by blists - more mailing lists