This flag is only ever set for special pages acquired in blkback (and
blktap2) via alloc_empty_pages_and_pagevec(), so in a sense the PG_blkback
flag always does apply, but I suppose it would be safe to clear it in
blkback_pagemap_clear().
Jake
On Fri, Oct 16, 2009 at 12:50 AM, Jan Beulich <JBeulich@novell.com> wrote:
> This flag, introduced with blktap2, seems to be sticky when blktap2
isn''t
> actively involved in any operations, since blkback-pagemap.c is only ever
> setting or testing this bit. Shouldn''t blkback_pagemap_clear()
clear it?
>
> And it would seem to me that, for safety purposes, both PG_blkback and
> PG_netback should be included in the checks in mm/page_alloc.c which
> already look at PG_foreign and (for ix86) PG_pinned.
>
> Thanks, Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel