linux-kernel - Re: [patch] IA64: suppress return value of down_trylock() in salinfo_work_to

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 2 Aug 2008 19:44:09 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	Simon Horman <horms@...ge.net.au>
Cc:	linux-ia64@...r.kernel.org, linux-kernel@...r.kernel.org,
	Tony Luck <tony.luck@...el.com>, Keith Owens <kaos@....com.au>
Subject: Re: [patch] IA64: suppress return value of down_trylock() in salinfo_work_to_do()

On Sat, Aug 02, 2008 at 07:32:00PM -0600, Matthew Wilcox wrote:
> I can't say that I think this is a good idea.  Has anyone looked at what
> it would take to actually track this?  For example, could we ever have
> the situation where:

Looking at this a bit more deeply, it seems to be a simple abuse of a
semaphore.

It's used both to exclude other tasks in salinfo_event_read() and as a
wake queue from interrupt context.  I think what we want is something
more like this:

	spin_lock(&data_saved_lock);
	if (!worktodo) {
		if (O_NONBLOCK)
			spin_unlock()
			return;
		else
			add to wait queue
			spin_unlock()
			schedule()
			spin_lock()
	}

Then we can just use wake_up() from interrupt context.

Thoughts?  I don't have any idea how to generate salinfo events, so I
wouldn't be able to test.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/