From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Alan Cox <alan@redhat.com>
Subject: Re: linux-next: Tree for August 29
Date: Sun, 31 Aug 2008 14:32:30 +0200 [thread overview]
Message-ID: <200808311432.30496.bzolnier@gmail.com> (raw)
In-Reply-To: <20080829194010.5ca53e33.sfr@canb.auug.org.au>
Hi,
On Friday 29 August 2008, Stephen Rothwell wrote:
> Hi all,
>
> Changes since next-20080828:
All block issuses have been fixed now (thanks guys!)
but the new warning emerged:
sysctl table check failed: /kernel/pty/nr .1.62.2 No data
Pid: 1, comm: swapper Not tainted 2.6.27-rc3-00458-g0ea12ec-dirty #196
[<c012e004>] set_fail+0x30/0x39
[<c012e436>] sysctl_check_table+0x429/0x467
[<c012e44d>] sysctl_check_table+0x440/0x467
[<c012e44d>] sysctl_check_table+0x440/0x467
[<c01206d3>] __register_sysctl_paths+0xab/0x23c
[<c02f8fb9>] mutex_lock+0x15/0x23
[<c015f0ed>] exact_lock+0x0/0xd
[<c012087e>] register_sysctl_paths+0x1a/0x1c
[<c03d8106>] pty_init+0x215/0x293
[<c0101122>] _stext+0x3a/0x12a
[<c03d7ef1>] pty_init+0x0/0x293
[<c018a1a8>] create_proc_entry+0x72/0x84
[<c013ea0d>] register_irq_proc+0x6b/0x84
[<c03c443b>] kernel_init+0x6d/0xb9
[<c03c43ce>] kernel_init+0x0/0xb9
[<c01037f3>] kernel_thread_helper+0x7/0x10
=======================
git bisect points at:
commit 0ea12ecc2f11ab28478939a5902505bd47f9b765
Author: Alan Cox <alan@redhat.com>
Date: Fri Aug 29 09:28:10 2008 +1000
tty-driver-kref
and somehow the following chunk looks suspicious:
--- a/drivers/char/pty.c
+++ b/drivers/char/pty.c
@@ -571,8 +571,11 @@ static void __init unix98_pty_init(void)
if (tty_register_driver(pts_driver))
panic("Couldn't register Unix98 pts driver");
+ /* FIXME: WTF */
+#if 0
pty_table[1].data = &ptm_driver->refcount;
- register_sysctl_table(pty_root_table);
+#endif
+ register_sysctl_table(pty_root_table);
/* Now create the /dev/ptmx special device */
tty_default_fops(&ptmx_fops);
Unfortunately it cannot be simply reverted so it seems
like WTF part will need some work after all... ;)
next prev parent reply other threads:[~2008-08-31 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 9:40 linux-next: Tree for August 29 Stephen Rothwell
2008-08-31 9:14 ` KAMEZAWA Hiroyuki
2008-08-31 12:32 ` Bartlomiej Zolnierkiewicz [this message]
2008-09-01 9:33 ` Alan Cox
2008-09-01 16:33 ` Bartlomiej Zolnierkiewicz
2008-09-01 22:24 ` Alan Cox
2008-09-02 10:41 ` Bartlomiej Zolnierkiewicz
2008-09-02 12:25 ` Takashi Iwai
2008-09-02 17:13 ` Bartlomiej Zolnierkiewicz
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=200808311432.30496.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).