From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-171.mta1.migadu.com (out-171.mta1.migadu.com [95.215.58.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1FC1B3E92B9 for ; Tue, 10 Mar 2026 20:18:15 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.171 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773173898; cv=none; b=bgt+0NVHULkGgrlFpH/3syqLtdPpgrlIj7meC79bepeqWp4HfUzv4z94QhZsUULdv0h4jlKcTsR1JTvF2Ltt3PuEHcEH2rqySjOome0dH89gnA1hODTNiFbB7IT56AnN/b/POyyVvWG/OqvZu4Sb9ykaKAn7QezMYCjL5cH8h+g= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773173898; c=relaxed/simple; bh=l7YqOaZ9Cxh9OXa7MgS8e984/y7Zy/UdguEwUSgLLeU=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=rb1snnrgKKOvmI0xelHWODU7RBVsIlYjGXWM7+6zjDyF4K+EHEW9ma5FqpW6whWPONkV6MDaC/S+CsYqpXc+Lanm1KpR9R0reDuASBUw2uuCr6PG1uaLMIeFQUO26G3/qqM/tr6f/QnqgUmTNnBj7sL0jP6cdRGXJQfL4Zarhco= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=uNHjGrUK; arc=none smtp.client-ip=95.215.58.171 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="uNHjGrUK" Date: Tue, 10 Mar 2026 13:18:03 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1773173894; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=fo82tIF5+QnwYHGL8br4DawXmsD1Q8bLn239Zv/oPPQ=; b=uNHjGrUKra94eH3gTyRIEQ0bcFls29b3XMpYdV5WnmB3mrDzx1L4Q+tXUXL/4Wb9sXaraN /ghkAe4VwmTQLIRFKVMrm3AcCC4uVXx/6hQBdzMweVM4SBRC/f7T0HdblLTkhXfZRAc47F JWHcbPRDUTCvqa4XetG6PebEo03j5wU= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Shakeel Butt To: Waiman Long Cc: Johannes Weiner , Michal Hocko , Roman Gushchin , Muchun Song , Andrew Morton , Tejun Heo , Michal =?utf-8?Q?Koutn=C3=BD?= , Shuah Khan , Mike Rapoport , linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, linux-mm@kvack.org, linux-kselftest@vger.kernel.org Subject: Re: [PATCH v2] selftest: memcg: Skp memcg_sock test if address family not supported Message-ID: References: <20260310143936.720592-1-longman@redhat.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260310143936.720592-1-longman@redhat.com> X-Migadu-Flow: FLOW_OUT On Tue, Mar 10, 2026 at 10:39:35AM -0400, Waiman Long wrote: > The test_memcg_sock test in memcontrol.c sets up an IPv6 socket and > send data over it to consume memory and verify that memory.stat.sock > and memory.current values are close. > > On systems where IPv6 isn't enabled or not configured to support > SOCK_STREAM, the test_memcg_sock test always fails. When the socket() > call fails, there is no way we can test the memory consumption and > verify the above claim. I believe it is better to just skip the test > in this case instead of reporting a test failure hinting that there > may be something wrong with the memcg code. > > Fixes: 5f8f019380b8 ("selftests: cgroup/memcontrol: add basic test for socket accounting") > Signed-off-by: Waiman Long Acked-by: Shakeel Butt