mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yu Zhang <yuz08559@gmail.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Linus Walleij <linusw@kernel.org>,
	Koichiro Den <koichiro.den@canonical.com>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] gpio: sim: fix the configfs lockup racing with mkdir/rmdir
Date: Sat, 31 Oct 2026 18:49:43 +1000	[thread overview]
Message-ID: <20261031084943.23107-1-yuz08559@gmail.com> (raw)
In-Reply-To: <CAMRc=MfuDQ9=bPYsxeEiRaLzC0Q+hVxjTov_JEGv_hsARM3U7g@mail.gmail.com>

On Wed, Oct 28, 2026 at 03:07:55AM -0700, Bartosz Golaszewski wrote:
> Is this in any way linked to your other patch[1] for gpio-sim? If so, and if
> this one is in response to sashiko reviews, please indicate it by keeping the
> series versioning, even if you changed the approach, otherwise, I can't know
> if the other one should be dropped or not?

Yes, v2 replaces [1], please drop it. Sashiko was right that v1 still
raced with mkdir/rmdir (it depended on the entries after dropping
dev->lock), so I redid the fix and changed the subject, but forgot to
put a changelog under the ---. Sorry about that.

> Maybe:
> 		num += list_count_nodes(&bank->line_list)

Done in v3, with the full history under the ---.

Thanks,
Yu

  reply	other threads:[~2026-10-31  8:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26  6:00 [PATCH] gpio: sim: snapshot configfs leaf items before depending on them Yu Zhang
2026-10-27  8:56 ` [PATCH v2] gpio: sim: fix the configfs lockup racing with mkdir/rmdir Yu Zhang
2026-10-28 10:07   ` Bartosz Golaszewski
2026-10-31  8:49     ` Yu Zhang [this message]
2026-10-31  8:58   ` [PATCH v3] " Yu Zhang

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=20261031084943.23107-1-yuz08559@gmail.com \
    --to=yuz08559@gmail.com \
    --cc=brgl@kernel.org \
    --cc=koichiro.den@canonical.com \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®