From mboxrd@z Thu Jan 1 00:00:00 1970 From: yamamoto-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org (YAMAMOTO Takashi) Subject: Re: [PATCH -mm 5/5] swapcgroup (v3): implement force_empty Date: Fri, 4 Jul 2008 16:48:28 +0900 (JST) Message-ID: <20080704074828.330DC5A19@siro.lan> References: <20080704162629.b06b6810.nishimura@mxp.nes.nec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Your message of "Fri, 4 Jul 2008 16:26:29 +0900" <20080704162629.b06b6810.nishimura-YQH0OdQVrdy45+QrQBaojngSJqDPrsil@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: nishimura-YQH0OdQVrdy45+QrQBaojngSJqDPrsil@public.gmane.org Cc: linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org, kosaki.motohiro-+CUm20s59erQFUHtdCDX3A@public.gmane.org, containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org, hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org, xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org, balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org List-Id: containers.vger.kernel.org > Hi, Yamamoto-san. > > Thank you for your comment. > > On Fri, 4 Jul 2008 15:54:31 +0900 (JST), yamamoto-jCdQPDEk3idL9jVzuh4AOg@public.gmane.org (YAMAMOTO Takashi) wrote: > > hi, > > > > > +/* > > > + * uncharge all the entries that are charged to the group. > > > + */ > > > +void __swap_cgroup_force_empty(struct mem_cgroup *mem) > > > +{ > > > + struct swap_info_struct *p; > > > + int type; > > > + > > > + spin_lock(&swap_lock); > > > + for (type = swap_list.head; type >= 0; type = swap_info[type].next) { > > > + p = swap_info + type; > > > + > > > + if ((p->flags & SWP_ACTIVE) == SWP_ACTIVE) { > > > + unsigned int i = 0; > > > + > > > + spin_unlock(&swap_lock); > > > > what prevents the device from being swapoff'ed while you drop swap_lock? > > > Nothing. > > After searching the entry to be uncharged(find_next_to_unuse below), > I recheck under swap_lock whether the entry is charged to the group. > Even if the device is swapoff'ed, swap_off must have uncharged the entry, > so I don't think it's needed anyway. > > > YAMAMOTO Takashi > > > > > + while ((i = find_next_to_unuse(p, i, mem)) != 0) { > > > + spin_lock(&swap_lock); > > > + if (p->swap_map[i] && p->memcg[i] == mem) > Ah, I think it should be added !p->swap_map to check the device has not > been swapoff'ed. find_next_to_unuse seems to have fragile assumptions and can dereference p->swap_map as well. YAMAMOTO Takashi > > > Thanks, > Daisuke Nishimura. > > > > + swap_cgroup_uncharge(p, i); > > > + spin_unlock(&swap_lock); > > > + } > > > + spin_lock(&swap_lock); > > > + } > > > + } > > > + spin_unlock(&swap_lock); > > > + > > > + return; > > > +} > > > #endif