linux-kernel - [GIT PULL] convert DRBD to REQ

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]

Message-Id: <201010231318.33517.philipp.reisner@linbit.com>
Date:	Sat, 23 Oct 2010 13:18:33 +0200
From:	Philipp Reisner <philipp.reisner@...bit.com>
To:	Jens Axboe <jaxboe@...ionio.com>
Cc:	Christoph Hellwig <hch@....de>, linux-kernel@...r.kernel.org
Subject: [GIT PULL] convert DRBD to REQ_FLUSH/FUA

Hi Jens,

Christoph Hellwig pointed out that drbd is the only driver
that still uses/supports barriers instead of FUE in linux-next.

I revitalized three patches that remove the barrier bits from DRBD...

The following changes since commit 8825f7c3e5c7b251b49fc594658a96f59417ee16:

  drbd: Silenced an assert (2010-10-22 15:55:22 +0200)

are available in the git repository at:
  git://git.drbd.org/linux-2.6-drbd.git for-jens

Philipp Reisner (3):
      drbd: Removed the BIO_RW_BARRIER support form the receiver/epoch code
      drbd: REQ_HARDBARRIER -> REQ_FUA transition for meta data accesses
      drbd: Removed checks for REQ_HARDBARRIER on incomming BIOs

 drivers/block/drbd/drbd_actlog.c   |   16 +---
 drivers/block/drbd/drbd_int.h      |   20 +---
 drivers/block/drbd/drbd_main.c     |    7 +-
 drivers/block/drbd/drbd_nl.c       |    8 +-
 drivers/block/drbd/drbd_proc.c     |    1 -
 drivers/block/drbd/drbd_receiver.c |  212 +++++-------------------------------
 drivers/block/drbd/drbd_req.c      |   14 ---
 drivers/block/drbd/drbd_worker.c   |   21 ----
 8 files changed, 40 insertions(+), 259 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/