linux-ext4 - Re: [PATCH 2/2] Don't hold spinlock while calling ext4_issue

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] [day] [month] [year] [list]

Message-ID: <20100920134423.GH3554@thunk.org>
Date:	Mon, 20 Sep 2010 09:44:23 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Lukas Czerner <lczerner@...hat.com>
Cc:	linux-ext4@...r.kernel.org, sandeen@...hat.com, adilger@...ger.ca
Subject: Re: [PATCH 2/2] Don't hold spinlock while calling
 ext4_issue_discard()

On Fri, Sep 10, 2010 at 08:51:31PM +0200, Lukas Czerner wrote:
> We can't hold spinlock because we can get rescheduled.
> 
> Signed-off-by: Lukas Czerner <lczerner@...hat.com>

Thanks, added to the ext4 patch queue.  For both patches I adjusted
the patch summary to be a bit more descriptive:

0dc23a4 ext4: don't hold spinlock while calling ext4_issue_discard()
9c54307 ext4: Check for negative error code from sb_issue_discard

It makes it easier to figure out which patches are which when you use
"git log --oneline".

					- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html