linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	oliver.sang@intel.com, ebiederm@xmission.com,
	colin.king@canonical.com, josh@joshtriplett.org,
	penberg@cs.helsinki.fi, mingo@elte.hu, jes@sgi.com, hch@lst.de,
	aia21@cantab.net, arjan@infradead.org, jgarzik@pobox.com,
	neukum@fachschaft.cup.uni-muenchen.de, oliver@neukum.name,
	dada1@cosmosbay.com, axboe@kernel.dk, axboe@suse.de,
	nickpiggin@yahoo.com.au, dhowells@redhat.com, nathans@sgi.com,
	rolandd@cisco.com, tytso@mit.edu, bunk@stusta.de,
	pbadari@us.ibm.com, ak@linux.intel.com, ak@suse.de,
	davem@davemloft.net, jsipek@cs.sunysb.edu, jens.axboe@oracle.com,
	ramsdell@mitre.org, hch@infradead.org, akpm@linux-foundation.org,
	randy.dunlap@oracle.com, efault@gmx.de, rdunlap@infradead.org,
	haveblue@us.ibm.com, drepper@redhat.com, dm.n9107@gmail.com,
	jblunck@suse.de, davidel@xmailserver.org,
	mtk.manpages@googlemail.com, linux-arch@vger.kernel.org,
	vda.linux@googlemail.com, jmorris@namei.org, serue@us.ibm.com,
	hca@linux.ibm.com, rth@twiddle.net, lethal@linux-sh.org,
	tony.luck@intel.com, heiko.carstens@de.ibm.com,
	andi@firstfloor.org, corbet@lwn.net, crquan@gmail.com,
	mszeredi@suse.cz, miklos@szeredi.hu, peterz@infradead.org,
	a.p.zijlstra@chello.nl, earl_chew@agilent.com, npiggin@gmail.com,
	npiggin@suse.de, julia@diku.dk, jaxboe@fusionio.com,
	nikai@nikai.net, dchinner@redhat.com, davej@redhat.com,
	npiggin@kernel.dk, eric.dumazet@gmail.com,
	tim.c.chen@linux.intel.com, xemul@parallels.com, tj@kernel.org,
	serge.hallyn@canonical.com, gorcunov@openvz.org, bcrl@kvack.org,
	alan@lxorguk.ukuu.org.uk, will.deacon@arm.com, will@kernel.org,
	zab@redhat.com, balbi@ti.com, gregkh@linuxfoundation.org,
	rusty@rustcorp.com.au, socketpair@gmail.com,
	penguin-kernel@i-love.sakura.ne.jp, mhocko@kernel.org,
	axboe@fb.com, tglx@linutronix.de, mcgrof@kernel.org,
	linux@dominikbrodowski.net, willy@infradead.org,
	paulmck@kernel.org, kernel@tuxforce.de,
	linux-morello@op-lists.linaro.org
Subject: Re: [RESEND PATCH] fs/pipe: Introduce a check to skip sleeping processes during pipe read/write
Date: Sat, 28 Dec 2024 17:32:32 +0100	[thread overview]
Message-ID: <20241228163231.GA19293@redhat.com> (raw)
In-Reply-To: <20241228152229.GC5302@redhat.com>

On 12/28, Oleg Nesterov wrote:
>
> If nothing else, consider
>
> 	int CONDITION;
> 	wait_queue_head_t WQ;
>
> 	void wake(void)
> 	{
> 		CONDITION = 1;
> 		wake_up(WQ);
> 	}
>
> 	void wait(void)
> 	{
> 		DEFINE_WAIT_FUNC(entry, woken_wake_function);
>
> 		add_wait_queue(WQ, entry);
> 		if (!CONDITION)
> 			wait_woken(entry, ...);
> 		remove_wait_queue(WQ, entry);
> 	}
>
> this code is correct even if LOAD(CONDITION) can leak into the critical
> section in add_wait_queue(), so CPU running wait() can actually do
>
> 		// add_wait_queue
> 		spin_lock(WQ->lock);
> 		LOAD(CONDITION);	// false!
> 		list_add(entry, head);
> 		spin_unlock(WQ->lock);
>
> 		if (!false)		// result of the LOAD above
> 			wait_woken(entry, ...);
>
> Now suppose that another CPU executes wake() between LOAD(CONDITION)
> and list_add(entry, head). With your patch wait() will miss the event.
> The same for __pollwait(), I think...
>
> No?

Even simpler,

	void wait(void)
	{
		DEFINE_WAIT(entry);

		__set_current_state(XXX);
		add_wait_queue(WQ, entry);

		if (!CONDITION)
			schedule();

		remove_wait_queue(WQ, entry);
		__set_current_state(TASK_RUNNING);
	}

This code is ugly but currently correct unless I am totally confused.

Oleg.


      reply	other threads:[~2024-12-28 16:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-25  9:42 [RESEND PATCH] fs/pipe: Introduce a check to skip sleeping processes during pipe read/write WangYuli
2024-12-25 13:30 ` Andy Shevchenko
2024-12-25 15:42   ` WangYuli
2024-12-26 16:00 ` Oleg Nesterov
2024-12-26 19:02 ` Linus Torvalds
2024-12-26 20:11   ` Oleg Nesterov
2024-12-27 18:39     ` Manfred Spraul
2024-12-28 14:32       ` Oleg Nesterov
2024-12-28 15:22         ` Oleg Nesterov
2024-12-28 16:32           ` Oleg Nesterov [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=20241228163231.GA19293@redhat.com \
    --to=oleg@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=aia21@cantab.net \
    --cc=ak@linux.intel.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andi@firstfloor.org \
    --cc=arjan@infradead.org \
    --cc=axboe@fb.com \
    --cc=axboe@kernel.dk \
    --cc=axboe@suse.de \
    --cc=balbi@ti.com \
    --cc=bcrl@kvack.org \
    --cc=brauner@kernel.org \
    --cc=bunk@stusta.de \
    --cc=colin.king@canonical.com \
    --cc=corbet@lwn.net \
    --cc=crquan@gmail.com \
    --cc=dada1@cosmosbay.com \
    --cc=davej@redhat.com \
    --cc=davem@davemloft.net \
    --cc=davidel@xmailserver.org \
    --cc=dchinner@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=dm.n9107@gmail.com \
    --cc=drepper@redhat.com \
    --cc=earl_chew@agilent.com \
    --cc=ebiederm@xmission.com \
    --cc=efault@gmx.de \
    --cc=eric.dumazet@gmail.com \
    --cc=gorcunov@openvz.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=haveblue@us.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jack@suse.cz \
    --cc=jaxboe@fusionio.com \
    --cc=jblunck@suse.de \
    --cc=jens.axboe@oracle.com \
    --cc=jes@sgi.com \
    --cc=jgarzik@pobox.com \
    --cc=jmorris@namei.org \
    --cc=josh@joshtriplett.org \
    --cc=jsipek@cs.sunysb.edu \
    --cc=julia@diku.dk \
    --cc=kernel@tuxforce.de \
    --cc=lethal@linux-sh.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-morello@op-lists.linaro.org \
    --cc=linux@dominikbrodowski.net \
    --cc=manfred@colorfullife.com \
    --cc=mcgrof@kernel.org \
    --cc=mhocko@kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mingo@elte.hu \
    --cc=mszeredi@suse.cz \
    --cc=mtk.manpages@googlemail.com \
    --cc=nathans@sgi.com \
    --cc=neukum@fachschaft.cup.uni-muenchen.de \
    --cc=nickpiggin@yahoo.com.au \
    --cc=nikai@nikai.net \
    --cc=npiggin@gmail.com \
    --cc=npiggin@kernel.dk \
    --cc=npiggin@suse.de \
    --cc=oliver.sang@intel.com \
    --cc=oliver@neukum.name \
    --cc=paulmck@kernel.org \
    --cc=pbadari@us.ibm.com \
    --cc=penberg@cs.helsinki.fi \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=peterz@infradead.org \
    --cc=ramsdell@mitre.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rdunlap@infradead.org \
    --cc=rolandd@cisco.com \
    --cc=rth@twiddle.net \
    --cc=rusty@rustcorp.com.au \
    --cc=serge.hallyn@canonical.com \
    --cc=serue@us.ibm.com \
    --cc=socketpair@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=tim.c.chen@linux.intel.com \
    --cc=tj@kernel.org \
    --cc=tony.luck@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=vda.linux@googlemail.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=will.deacon@arm.com \
    --cc=will@kernel.org \
    --cc=willy@infradead.org \
    --cc=xemul@parallels.com \
    --cc=zab@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).