linux-kernel - [GIT PULL] 4 fixes for drbd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 29 Oct 2012 15:48:29 +0100
From:	Philipp Reisner <philipp.reisner@...bit.com>
To:	Jens Axboe <axboe@...nel.dk>
Cc:	linux-kernel@...r.kernel.org, drbd-dev@...ts.linbit.com
Subject: [GIT PULL] 4 fixes for drbd

Hi Jens,

please consider to pull these fixes in. It is based on your
for-3.7/drivers branch.

Best regards,
 Phil


The following changes since commit 34a73dd594699dc3834167297a74c43948bb6e41:

  Revert "memstick: add support for legacy memorysticks" (2012-10-10 16:13:26 
-0600)

are available in the git repository at:

  git://git.drbd.org/linux-drbd.git for-jens

for you to fetch changes up to 731d4596a6f3ba41418a0b11018c453456c51d92:

  drbd: check return of kmalloc in receive_uuids (2012-10-29 13:18:13 +0100)

----------------------------------------------------------------
Jing Wang (1):
      drbd: check return of kmalloc in receive_uuids

Lars Ellenberg (2):
      drbd: fix regression: potential NULL pointer dereference
      drbd: don't try to clear bits once the disk has failed

Philipp Reisner (1):
      drbd: Broadcast sync progress no more often than once per second

 drivers/block/drbd/drbd_actlog.c   |   19 +++++++++++++------
 drivers/block/drbd/drbd_int.h      |    6 ++++++
 drivers/block/drbd/drbd_main.c     |    8 ++++++--
 drivers/block/drbd/drbd_nl.c       |    5 +++++
 drivers/block/drbd/drbd_receiver.c |    4 ++++
 drivers/block/drbd/drbd_worker.c   |    4 ++++
 6 files changed, 38 insertions(+), 8 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/