All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Deming Wang <wangdeming@inspur.com>
Cc: <shuah@kernel.org>, <linux-mm@kvack.org>,
	<linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] selftests/mm: Replace obsolete memalign() with posix_memalign()
Date: Thu, 13 Apr 2023 15:11:28 -0700	[thread overview]
Message-ID: <20230413151128.abd305c1689eeac237e4e4e7@linux-foundation.org> (raw)
In-Reply-To: <20230413012751.4445-1-wangdeming@inspur.com>

On Wed, 12 Apr 2023 21:27:51 -0400 Deming Wang <wangdeming@inspur.com> wrote:

> memalign() is obsolete according to its manpage.
> 
> Replace memalign() with posix_memalign().
> 
> As a pointer is passed into posix_memalign(),initialize *map to
> NULL,to silence a warning about the function's return value being
> used as uninitialized (which is not valid anyway because the
> error is properly checked before map is returned).
> 

The patch you sent doesn't do this?

> --- a/tools/testing/selftests/mm/soft-dirty.c
> +++ b/tools/testing/selftests/mm/soft-dirty.c
> @@ -80,9 +80,9 @@ static void test_hugepage(int pagemap_fd, int pagesize)
>  	int i, ret;
>  	size_t hpage_len = read_pmd_pagesize();
>  
> -	map = memalign(hpage_len, hpage_len);
> -	if (!map)
> -		ksft_exit_fail_msg("memalign failed\n");
> +	ret = posix_memalign((void **)(&map), hpage_len, hpage_len);
> +	if (ret < 0)
> +		ksft_exit_fail_msg("posix_memalign failed\n");
>  
>  	ret = madvise(map, hpage_len, MADV_HUGEPAGE);
>  	if (ret)


  reply	other threads:[~2023-04-13 22:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13  1:27 [PATCH] selftests/mm: Replace obsolete memalign() with posix_memalign() Deming Wang
2023-04-13 22:11 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-12  9:35 Deming Wang
2023-04-12  7:27 Deming Wang
2023-04-12  8:25 ` David Hildenbrand
2023-04-12  6:58 Deming Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230413151128.abd305c1689eeac237e4e4e7@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shuah@kernel.org \
    --cc=wangdeming@inspur.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.