Re: [PATCH 0/5] v2: block subsystem refcounter conversions

On Fri, 2017-04-21 at 14:30 -0700, Kees Cook wrote: > On Fri, Apr 21, 2017 at 2:27 PM, James Bottomley > <james.bottom...@hansenpartnership.com> wrote: > > On Fri, 2017-04-21 at 13:22 -0700, Kees Cook wrote: > > > On Fri, Apr 21, 2017 at 12:55 PM, Eric Biggers

Re: [PATCH 0/5] v2: block subsystem refcounter conversions

On Fri, 2017-04-21 at 13:22 -0700, Kees Cook wrote: > On Fri, Apr 21, 2017 at 12:55 PM, Eric Biggers > wrote: > > > > Of course, having extra checks behind a debug option is fine. > > > > But they should not be part of the base feature; the base > > > > feature should

Re: [PATCH 0/5] block subsystem refcounter conversions

On Mon, 2017-02-20 at 17:56 +0100, Peter Zijlstra wrote: > On Mon, Feb 20, 2017 at 07:41:01AM -0800, James Bottomley wrote: > > On Mon, 2017-02-20 at 08:15 -0700, Jens Axboe wrote: > > > On 02/20/2017 04:16 AM, Elena Reshetova wrote: > > > > Now when new refcount_t t

Re: [PATCH 0/5] block subsystem refcounter conversions

On Mon, 2017-02-20 at 08:15 -0700, Jens Axboe wrote: > On 02/20/2017 04:16 AM, Elena Reshetova wrote: > > Now when new refcount_t type and API are finally merged > > (see include/linux/refcount.h), the following > > patches convert various refcounters in the block susystem from > > atomic_t to

Re: LSF/MM 2017: Call for Proposals

On Thu, 2016-12-08 at 13:26 +0100, Michal Hocko wrote: > On Wed 07-12-16 06:57:06, James Bottomley wrote: > [...] > > Just on this point, since there seems to be a lot of confusion: lsf > > -pc > > is the list for contacting the programme committee, so

Re: LSF/MM 2017: Call for Proposals

On Thu, 2016-12-01 at 09:11 -0500, Jeff Layton wrote: > 1) Proposals for agenda topics should be sent before January 15th, > 2016 to: > > lsf...@lists.linux-foundation.org > > and cc the Linux list or lists that are relevant for the topic in > question: > > ATA:

[PATCH] btrfs: fix compile failure on parisc

:206: warning: assignment makes pointer from integer without a cast fs/btrfs/raid56.c:226: error: implicit declaration of function 'vfree' make[2]: *** [fs/btrfs/raid56.o] Error 1 Fix this by adding vmalloc.h explicitly to the includes list Signed-off-by: James Bottomley jbottom...@parallels.com

Re: btrfs for enterprise raid arrays

On Fri, 2009-04-03 at 06:27 -0700, Matthew Wilcox wrote: On Fri, Apr 03, 2009 at 12:58:00PM +0100, David Woodhouse wrote: On Fri, 2009-04-03 at 12:43 +0100, Ric Wheeler wrote: New firmware/microcode versions are able to reclaim that space if it sees a certain number of consecutive

Re: btrfs for enterprise raid arrays

On Fri, 2009-04-03 at 07:43 -0400, Ric Wheeler wrote: Erwin van Londen wrote: Another thing is that some arrays have the capability to thin-provision volumes. In the back-end on the physical layer the array configures, let say, a 1 TB volume and virtually provisions 5TB to the host. On