• P
    livepatch: Initialize shadow variables safely by a custom callback · e91c2518
    Petr Mladek 提交于
    The existing API allows to pass a sample data to initialize the shadow
    data. It works well when the data are position independent. But it fails
    miserably when we need to set a pointer to the shadow structure itself.
    
    Unfortunately, we might need to initialize the pointer surprisingly
    often because of struct list_head. It is even worse because the list
    might be hidden in other common structures, for example, struct mutex,
    struct wait_queue_head.
    
    For example, this was needed to fix races in ALSA sequencer. It required
    to add mutex into struct snd_seq_client. See commit b3defb79
    ("ALSA: seq: Make ioctls race-free") and commit d15d662e
    ("ALSA: seq: Fix racy pool initializations")
    
    This patch makes the API more safe. A custom constructor function and data
    are passed to klp_shadow_*alloc() functions instead of the sample data.
    
    Note that ctor_data are no longer a template for shadow->data. It might
    point to any data that might be necessary when the constructor is called.
    
    Also note that the constructor is called under klp_shadow_lock. It is
    an internal spin_lock that synchronizes alloc() vs. get() operations,
    see klp_shadow_get_or_alloc(). On one hand, this adds a risk of ABBA
    deadlocks. On the other hand, it allows to do some operations safely.
    For example, we could add the new structure into an existing list.
    This must be done only once when the structure is allocated.
    Reported-by: NNicolai Stange <nstange@suse.de>
    Signed-off-by: NPetr Mladek <pmladek@suse.com>
    Acked-by: NJosh Poimboeuf <jpoimboe@redhat.com>
    Acked-by: NMiroslav Benes <mbenes@suse.cz>
    Signed-off-by: NJiri Kosina <jkosina@suse.cz>
    e91c2518
livepatch-shadow-fix2.c 3.5 KB