public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel: sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice Sysctl already exists
Date: Fri, 30 May 2008 11:19:28 -0700	[thread overview]
Message-ID: <m1wslb1wpb.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <20080530150515.GA30397@redhat.com> (Dave Jones's message of "Fri, 30 May 2008 11:05:15 -0400")

Dave Jones <davej@redhat.com> writes:

> Well, that's umm, special.
> I wonder if powering off the printer isn't causing the sysctl to be removed,
> causing the next power-on to look like a new device ?
> Eric, you poked around the sysctl paths in parport last year, any ideas?

Yes.  The short answer is that this is a real bug in the parport code
that has existed forever.  We just now complain.

http://bugzilla.kernel.org/show_bug.cgi?id=9749

It takes something like two accessors of the parallel port to trigger
this.  Though not in a bad way.

In particular each open creates the sysctl for the duration of the
open (or something like that) and so if you open (I think it is
/dev/parport0) twice you try and create the sysctls twice.

I got as far as basic confirmation of this bug, and a rough cause of
it.  Unfortunately I have not had the time to unscramble it, and neither
it seems has anyone else.

Eric

      reply	other threads:[~2008-05-30 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 15:05 kernel: sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice Sysctl already exists Dave Jones
2008-05-30 18:19 ` Eric W. Biederman [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=m1wslb1wpb.fsf@frodo.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@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