Re: [RFC][PATCH 2/5] add SWAP_HAS_CACHE flag to swap_map

From: Daisuke Nishimura
Date: Wed May 27 2009 - 20:45:25 EST


> @@ -1969,17 +2017,33 @@ int swap_duplicate(swp_entry_t entry)
> offset = swp_offset(entry);
>
> spin_lock(&swap_lock);
> - if (offset < p->max && p->swap_map[offset]) {
> - if (p->swap_map[offset] < SWAP_MAP_MAX - 1) {
> - p->swap_map[offset]++;
> +
> + if (unlikely(offset >= p->max))
> + goto unlock_out;
> +
> + count = swap_count(p->swap_map[offset]);
> + has_cache = swap_has_cache(p->swap_map[offset]);
> + if (cache) {
> + /* set SWAP_HAS_CACHE if there is no cache and entry is used */
> + if (!has_cache && count) {
Should we check !has_cache here ?

Concurrent read_swap_cache_async() might have set SWAP_HAS_CACHE, but not have added
a page to swap cache yet when find_get_page() was called.
add_to_swap_cache() would handle the race of concurrent read_swap_cache_async(),
but considering more, swapcache_free() at the end of the loop might dangerous in this case...
So I think it should be like:

read_swap_cache_async()
:
valid = swapcache_prepare(entry);
if (!valid)
break;
if (valid == -EAGAIN);
continue;

to let the context that succeeded in swapcache_prepare() do add_to_swap_cache().


Thanks,
Daisuke Nishimura.

> + p->swap_map[offset] = make_swap_count(count, 1);
> + result = 1;
> + }
> + } else if (count || has_cache) {
> + if (count < SWAP_MAP_MAX - 1) {
> + p->swap_map[offset] = make_swap_count(count + 1,
> + has_cache);
> result = 1;
> - } else if (p->swap_map[offset] <= SWAP_MAP_MAX) {
> + } else if (count <= SWAP_MAP_MAX) {
> if (swap_overflow++ < 5)
> - printk(KERN_WARNING "swap_dup: swap entry overflow\n");
> - p->swap_map[offset] = SWAP_MAP_MAX;
> + printk(KERN_WARNING
> + "swap_dup: swap entry overflow\n");
> + p->swap_map[offset] = make_swap_count(SWAP_MAP_MAX,
> + has_cache);
> result = 1;
> }
> }
> +unlock_out:
> spin_unlock(&swap_lock);
> out:
> return result;
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/