From: Majkls <majkls@tiscali.cz>
To: linux-fsdevel@vger.kernel.org
Subject: Re: CVE-2006-3468
Date: Thu, 16 Nov 2006 22:49:53 +0100 [thread overview]
Message-ID: <455CDD01.9020207@tiscali.cz> (raw)
In-Reply-To: <455CDC3B.1080707@tiscali.cz>
Matthew Wilcox wrote:
>> On Thu, Nov 16, 2006 at 10:21:32PM +0100, Majkls wrote:
>>
>
>>>>Hello,
>>>>I would like to solve this bug. Have anybody some backtrace or some
>>>>working exploit?
>
>>
>>
>> Sure you have the right CVE? That bug seems to have been fixed long
>> ago:
>>
>>
http://git.parisc-linux.org/?p=linux-2.6.git;a=commit;h=2ccb48ebb4de139eef4fcefd5f2bb823cb0d81b9
Thanks. I did not know about it. So there is a question. How are the
advisories on secunia updated. They are still reporting that this bug is
not fixed. http://secunia.com/advisories/21369/
>> -
>> To unsubscribe from this list: send the line "unsubscribe
linux-fsdevel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
-- Miloslav "Majkls" Semler
prev parent reply other threads:[~2006-11-16 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 21:21 CVE-2006-3468 Majkls
2006-11-16 21:31 ` CVE-2006-3468 Matthew Wilcox
[not found] ` <455CDC3B.1080707@tiscali.cz>
2006-11-16 21:49 ` Majkls [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=455CDD01.9020207@tiscali.cz \
--to=majkls@tiscali.cz \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).