linux-kernel - handle memory allocation failure

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

Date:	Tue, 19 Feb 2008 23:13:33 +0100
From:	Jim Meyering <jim@...ering.net>
To:	linux-kernel@...r.kernel.org
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Markus Armbruster <armbru@...hat.com>,
	Jim Meyering <jim@...ering.net>
Subject: handle memory allocation failure

Hello,

I spotted a few unchecked memory allocation failures recently,
and went looking for more.  I found and fixed seven others.
I posted them all in one change-set, here:
Thanks again to Markus Armbruster for a rigorous review.

    Subject: [PATCH] Handle memory allocation failure.
    http://thread.gmane.org/gmane.linux.kernel/636710

Andrew Morton suggested posting them separately, with each
subject indicating the affected subsection, per #14 in
Documentation/SubmittingPatches, so this series is the result:

    Subject: [PATCH] alpha: handle kcalloc failure
    Subject: [PATCH] 9p: handle kstrdup and match_strdup failure
    Subject: [PATCH] affs: handle match_strdup failure
    Subject: [PATCH] hfs: handle match_strdup failure
    Subject: [PATCH] hfsplus: handle match_strdup failure
    Subject: [PATCH] usbaudio: handle kcalloc failure
--
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/