From: Horms <horms@verge.net.au>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Colin Leroy <colin@colino.net>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org, debian-kernel@lists.debian.org
Subject: Re: [PATCH] hfs, hfsplus: don't leak s_fs_info and fix an oops
Date: Fri, 7 Oct 2005 13:39:27 +0900 [thread overview]
Message-ID: <20051007043924.GA20827@verge.net.au> (raw)
I have been looking over CAN-2005-3109, better known as
the hfs, hfsplus leak and oops, and I am wondering if the
problem is present in 2.4
I took a look at making a backport, and it seems that
some of the problems are there, but without a deeper inspection
of the code its difficult to tell if the problems manifest or not.
For reference, here is the 2.6 variant of the change:
http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=945b092011c6af71a0107be96e119c8c08776f3f
I can futher my backport effort and post it for inspection if need be.
--
Horms
next reply other threads:[~2005-10-07 4:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 4:39 Horms [this message]
2005-10-07 7:10 ` [PATCH] hfs, hfsplus: don't leak s_fs_info and fix an oops Colin Leroy
2005-10-07 7:31 ` Horms
2005-11-29 4:16 ` Horms
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=20051007043924.GA20827@verge.net.au \
--to=horms@verge.net.au \
--cc=colin@colino.net \
--cc=debian-kernel@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=zippel@linux-m68k.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