All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: cem@kernel.org, hch@lst.de, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/7] xfs: port healthmon event list to list_head
Date: Mon, 31 Aug 2026 08:58:26 +0200	[thread overview]
Message-ID: <20260831065826.GC24602@lst.de> (raw)
In-Reply-To: <178780640625.3528467.15741375660976356976.stgit@frogsfrogsfrogs>

On Wed, Aug 26, 2026 at 10:32:59PM -0700, Darrick J. Wong wrote:
>  struct xfs_healthmon_event {
> -	struct xfs_healthmon_event	*next;
> +	struct list_head		list;

Call this entry to make clear it's a list entry and not the list?

> +static inline struct xfs_healthmon_event *xfs_healthmon_alloc_event(void)
> +{
> +	struct xfs_healthmon_event		*event =
> +		kzalloc_obj(struct xfs_healthmon_event, GFP_NOFS);
> +
> +	if (event)
> +		INIT_LIST_HEAD(&event->list);
> +	return event;

There is no need to initialize a list_head only used as an entry.

> +}
> +
> +static inline struct xfs_healthmon_event *
> +xfs_healthmon_dup_event(
> +	const struct xfs_healthmon_event	*template)
> +{
> +	struct xfs_healthmon_event		*event =
> +		kmemdup(template, sizeof(struct xfs_healthmon_event),
> +				GFP_NOFS);
> +
> +	if (event)
> +		INIT_LIST_HEAD(&event->list);
> +	return event;

Same here.


  parent reply	other threads:[~2026-08-31  6:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-27  5:31 [PATCHSET v2 2/2] xfs: LLM-inspired bug fixes, part 8 Darrick J. Wong
2026-08-27  5:32 ` [PATCH 1/7] xfs: always set xfs_healthmon::first_event when inserting at front of list Darrick J. Wong
2026-08-31  6:54   ` Christoph Hellwig
2026-08-27  5:32 ` [PATCH 2/7] xfs: port healthmon event list to list_head Darrick J. Wong
2026-08-27  9:33   ` Anuj Gupta
2026-08-27 14:47     ` Darrick J. Wong
2026-08-31  6:58       ` Christoph Hellwig
2026-08-31 14:53         ` Darrick J. Wong
2026-08-31  6:58   ` Christoph Hellwig [this message]
2026-08-31 15:12     ` Darrick J. Wong
2026-08-27  5:33 ` [PATCH 3/7] xfs: check healthmon outbuffer space correctly Darrick J. Wong
2026-08-31  6:59   ` Christoph Hellwig
2026-08-27  5:33 ` [PATCH 4/7] xfs: merge healthmon insert/push helpers Darrick J. Wong
2026-08-31  6:59   ` Christoph Hellwig
2026-08-27  5:33 ` [PATCH 5/7] xfs: bump lost_prev_errors if we lose even the healthmon lost event Darrick J. Wong
2026-08-27  5:34 ` [PATCH 6/7] xfs: report nonexistent parents as a filesystem corruption Darrick J. Wong
2026-08-27  5:34 ` [PATCH 7/7] xfs: destroy seen inode bitmap when we fail to add a dirpath Darrick J. Wong

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=20260831065826.GC24602@lst.de \
    --to=hch@lst.de \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    /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.