summaryrefslogtreecommitdiff
path: root/include/crypto/sha1_base.h
diff options
context:
space:
mode:
authorTakashi Iwai <tiwai@suse.de>2017-02-08 12:35:39 +0100
committerTakashi Iwai <tiwai@suse.de>2017-02-08 12:42:37 +0100
commit4842e98f26dd80be3623c4714a244ba52ea096a8 (patch)
tree08e56d4db3d9f4d720fbaf3091d31ff219c5b58e /include/crypto/sha1_base.h
parentf3d83317a69e7d658e7c83e24f8b31ac533c39e3 (diff)
ALSA: seq: Fix race at creating a queue
When a sequencer queue is created in snd_seq_queue_alloc(),it adds the new queue element to the public list before referencing it. Thus the queue might be deleted before the call of snd_seq_queue_use(), and it results in the use-after-free error, as spotted by syzkaller. The fix is to reference the queue object at the right time. Reported-by: Dmitry Vyukov <dvyukov@google.com> Cc: <stable@vger.kernel.org> Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'include/crypto/sha1_base.h')
0 files changed, 0 insertions, 0 deletions
eptional DAX entries (a bug which is there for a long time) - without these patches data loss can occur on power failure even though user called fsync(2). The other three patches change locking of DAX faults so that ->iomap_begin() is called in a more relaxed locking context and we are safe to start a transaction there for ext4" These have received a build success notification from the kbuild robot, and pass the latest libnvdimm unit tests. There have not been any -next releases since -rc1, so they have not appeared there" * 'libnvdimm-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm: ext4: Simplify DAX fault path dax: Call ->iomap_begin without entry lock during dax fault dax: Finish fault completely when loading holes dax: Avoid page invalidation races and unnecessary radix tree traversals mm: Invalidate DAX radix tree entries only if appropriate ext2: Return BH_New buffers for zeroed blocks
Diffstat (limited to 'tools/perf/Documentation')