From: Christian Kujau <evil@g-house.de>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@osdl.org>, Greg KH <greg@kroah.com>,
Pekka Enberg <penberg@gmail.com>,
Matt_Domsch@dell.com
Subject: Re: [PATCH] kobject: fix double kobject_put() in error path of kobject_add()
Date: Tue, 09 Nov 2004 23:06:34 +0100 [thread overview]
Message-ID: <41913F6A.5010806@g-house.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0411091108470.2301@ppc970.osdl.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
i'm sorry to say that it did not help:
http://www.nerdbynature.de/bits/prinz/2.6.10-rc1/dmesg-2.6.10-rc1_edd__kobject_put.txt
i'll go on and try to exclude
ChangeSet@1.2000.5.108, 2004-10-20 08:36:22-07:00, Matt_Domsch@dell.com
[PATCH] EDD: use EXTENDED READ command, add CONFIG_EDD_SKIP_MBR
(or just test /pub/linux/kernel/v2.6/snapshots/old/patch-2.6.9-bk*.gz ...)
thanks,
Christian.
- --
BOFH excuse #200:
The monitor needs another box of pixels.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBkT9q+A7rjkF8z0wRArHjAJ4qSyZf+ioC4VkvPxk2fCNWUrl18QCeLK85
8e2EyGuWgBviGETlV25t/XE=
=Qvnz
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-11-09 22:07 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4180F026.9090302@g-house.de>
2004-10-28 13:29 ` [Alsa-devel] Oops in 2.6.10-rc1 Jaroslav Kysela
2004-10-28 14:09 ` Christian
2004-11-04 15:16 ` Christian Kujau
2004-11-05 2:35 ` Christian Kujau
2004-11-07 1:24 ` Christian Kujau
2004-11-07 7:02 ` Linus Torvalds
2004-11-07 13:10 ` Christian Kujau
2004-11-07 16:02 ` Christian Kujau
2004-11-07 16:57 ` Linus Torvalds
2004-11-07 18:31 ` Christian Kujau
2004-11-07 18:44 ` Linus Torvalds
2004-11-07 23:45 ` Christian Kujau
2004-11-08 1:16 ` Linus Torvalds
2004-11-08 13:01 ` Christian Kujau
2004-11-08 18:13 ` Linus Torvalds
2004-11-08 20:59 ` Christian Kujau
2004-11-08 23:49 ` Christian Kujau
2004-11-09 1:05 ` Linus Torvalds
2004-11-09 1:41 ` Christian Kujau
2004-11-09 1:31 ` Christian Kujau
2004-11-09 7:40 ` Pekka Enberg
2004-11-09 12:33 ` Christian Kujau
2004-11-09 17:26 ` Oops in 2.6.10-rc1 (almost solved) Christian Kujau
2004-11-09 18:53 ` Linus Torvalds
2004-11-09 19:04 ` [PATCH] kobject: fix double kobject_put() in error path of kobject_add() Greg KH
2004-11-09 19:08 ` Greg KH
2004-11-09 20:19 ` Pekka Enberg
2004-11-09 21:21 ` Christian Kujau
2004-11-09 21:31 ` Christian Kujau
2004-11-09 19:09 ` Linus Torvalds
2004-11-09 22:06 ` Christian Kujau [this message]
2004-11-09 23:30 ` Oops in 2.6.10-rc1 (almost solved) Christian Kujau
2004-11-09 23:40 ` Matt Domsch
2004-11-10 0:21 ` Christian Kujau
2004-11-10 1:01 ` Linus Torvalds
2004-11-11 22:43 ` Matt Domsch
2004-11-11 22:53 ` Linus Torvalds
2004-11-11 22:55 ` Matt Domsch
2004-11-12 0:27 ` Christian Kujau
2004-11-12 0:49 ` Linus Torvalds
2004-11-12 1:27 ` Christian Kujau
2004-11-10 0:12 ` Oops in 2.6.10-rc1 Christian Kujau
2004-11-10 0:23 ` Linus Torvalds
2004-11-08 18:44 ` Pekka Enberg
2004-11-08 19:00 ` Greg KH
2004-11-08 19:18 ` Pekka Enberg
2004-11-08 19:30 ` Pekka Enberg
2004-11-08 20:31 ` Christian Kujau
2004-11-07 13:05 ` Pekka Enberg
2004-11-07 13:43 ` Christian Kujau
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=41913F6A.5010806@g-house.de \
--to=evil@g-house.de \
--cc=Matt_Domsch@dell.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@gmail.com \
--cc=torvalds@osdl.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