Re: Tapdisk2 problem

["Pasi Kärkkäinen" <pasik@iki.fi>]

On Mon, Aug 16, 2010 at 12:07:35AM +0200, Michael Brade wrote:
> On Sunday 15 August 2010 23:54:43 Daniel Stodden wrote:
> > On Sun, 2010-08-15 at 16:48 -0400, Keir Fraser wrote:
> > > On 15/08/2010 21:36, "Daniel Stodden" <daniel.stodden@citrix.com> wrote:
> > > > On Sun, 2010-08-15 at 16:28 -0400, Keir Fraser wrote:
> > > >> On 15/08/2010 20:35, "Daniel Stodden" <daniel.stodden@citrix.com> 
> wrote:
> > > >>> The problem is that the kernel has those changes. What's going to
> > > >>> happen is that if tapdisk2 anticipates the ring 'message' at offset
> > > >>> 17, not 16 as intended, it will fail to find/clear the ring message,
> > > >>> while the kernel will keep it spinning through select(), and that's
> > > >>> what you're seeing.
> > > >>> 
> > > >>> Keir, okay to just pull that stuff?
> > > >> 
> > > >> What stuff to where?
> > > > 
> > > > changeset:   21707:feee0abed6aa
> > > > user:        Keir Fraser <keir.fraser@citrix.com>
> > > > date:        Fri Jul 02 18:58:02 2010 +0100
> > > > summary:     blktap2: make protocol specific usage of shared sring
> > > > explicit
> > > > 
> > > > Into 4.0.1.
> > > 
> > > Okay, done.
> > 
> > Thanks!
> 
> Where can I find this change? I am using xen-4.0-testing.hg but the last chnage 
> is a few days old?
> 

It's in:
http://xenbits.xen.org/staging/xen-4.0-testing.hg

-- Pasi