The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Elizabeth Figura <zfigura@codeweavers.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Griffin Kroah-Hartman <griffin@kroah.com>,
	wine-devel@list.winehq.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ntsync: Check for owner in setup_wait()
Date: Thu, 16 Jul 2026 17:28:43 -0500	[thread overview]
Message-ID: <2446257.n0HT0TaD9V@camazotz> (raw)
In-Reply-To: <2026071516-unlucky-squad-2b68@gregkh>

On Tuesday, 14 July 2026 23:56:35 CDT Greg Kroah-Hartman wrote:
> On Tue, Jul 14, 2026 at 12:16:47PM -0500, Elizabeth Figura wrote:
> > On Tuesday, 14 July 2026 10:36:46 CDT Griffin Kroah-Hartman wrote:
> > > Add a check to see if any mutex owner is 0.
> > > 
> > > As stated in the uapi documentation , this is a failure case that was
> > > not being checked under the NTSYNC_IOC_WAIT_ANY and NTSYNC_IOC_WAIT_ALL
> > > cases, which state that mutexes with no owner should fail the ioctl with
> > > -EINVAL.
> > 
> > This has already been sent I'm afraid:
> > 
> > https://lore.kernel.org/all/20260628024239.152852-1-ivanrwcm25@gmail.com/
> 
> Cool, but that series wasn't sent to the maintainers to get them merged,
> and there's going to be a second version as it conflicts with your
> previous patches, right?
> 
> Or are you going to batch these up and send them to Arnd and me for
> inclusion later on?

Ah I'm sorry, I missed that those patches weren't sent to Arnd and you. I'll resend them. The previous patches are in the same situation, but I think these cover a superset of the same ground so I'll just send them alone.

> And is the wine-devel list still alive?  If not, we should probably drop
> that from the MAINTAINERS file.

It's alive, but the address moved. I forgot that this reference needed to be updated; I apologize for that. I sent a fix there as <https://lore.kernel.org/all/20260701183214.13973-1-zfigura@codeweavers.com/>. I guess that should also have been sent to you as the relevant subsystem maintainers; I failed to properly think that one through.



      reply	other threads:[~2026-07-16 22:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 15:36 [PATCH] ntsync: Check for owner in setup_wait() Griffin Kroah-Hartman
2026-07-14 17:16 ` Elizabeth Figura
2026-07-15  4:56   ` Greg Kroah-Hartman
2026-07-16 22:28     ` Elizabeth Figura [this message]

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=2446257.n0HT0TaD9V@camazotz \
    --to=zfigura@codeweavers.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=griffin@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wine-devel@list.winehq.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