linux-kernel - Re: [Drbd-dev] [PATCH 00/18] RFC: Non blocking submit for activity log misses

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130322200333.GI5231@soda.linbit>
Date:	Fri, 22 Mar 2013 21:03:33 +0100
From:	lars.ellenberg@...bit.com
To:	Jens Axboe <axboe@...nel.dk>
Cc:	Philipp Reisner <philipp.reisner@...bit.com>,
	linux-kernel@...r.kernel.org, drbd-dev@...ts.linbit.com
Subject: Re: [Drbd-dev] [PATCH 00/18] RFC: Non blocking submit for activity
 log misses

On Fri, Mar 22, 2013 at 11:17:06AM -0600, Jens Axboe wrote:
> On Tue, Mar 19 2013, Philipp Reisner wrote:

> > This patch series improves DRBD's behavior. A submitter is no longer blocked
> > in the case of a AL-miss. For this a dedicated submitter worker is introduced
> > (patch 13).

> Patchset doesn't apply to current tree. 10/18 gets into problems, last
> hunk of drbd_main.c. What is this based on?

I think it is just missing

  commit 56de210245487ef1f1416c8ec9e581ebdd0d32ec
  Author: Tejun Heo <tj@...nel.org>
  Date:   Wed Feb 27 17:04:01 2013 -0800
  
      drbd: convert to idr_alloc()
  
          Convert to the much saner new idr interface.

I'll post an updated 10/18 right away.

This RfC batch was produced from a tree
based more-or-less on your for-3.9-drivers, I think.

We will rebase to your for-3.10/drivers shortly,
and then also post an additional batch of general fixes.

	Lars

--
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/