From: Marc Dionne <marc.c.dionne@gmail.com>
To: linux-kernel@vger.kernel.org, sukadev@linux.vnet.ibm.com
Subject: Regression in 2.6.30 - /dev/pts - mount options - bisected
Date: Fri, 8 May 2009 17:54:34 -0400 [thread overview]
Message-ID: <6041d2000905081454x4c9d8818oaccbcd14d1f4a506@mail.gmail.com> (raw)
I ran into a regression from 2.6.29 to 2.6.30 on a newly installed
fedora 11 machine. The symptom is that things that require /dev/pts
(gnome-terminal, konsole, xterm, etc.) don't work for a regular user,
but run fine as root. Everything is fine with the fedora 2.6.29
kernel or with a self-compiled 2.6.29, but fail with a recent
2.6.30-rc.
Bisection pinpoints this commit:
http://git.kernel.org/linus/1bd7903560f1f713e85188a5aaf4d2428b6c8b50
as the culprit, although I think that's a bit misleading.
The commit moves code around, and along the way replaces this:
memcpy(&fsi->mount_opts, opts, sizeof(opts))
in one function where opts is a (struct pts_mount_opts *) - 8 bytes,
clearly an error, with
memcpy(&(DEVPTS_SB(s))->mount_opts, &opts, sizeof(opts));
in a different function where opts is an actual structure (24 bytes),
which looks like what was intended. So fixing the copy of the mount
options triggers the problem, and the real cause is probably
neighbouring commits in the same patch set. I confirmed that using
sizeof(&opts) in the above memcpy makes the problem go away (but is
obviously not a solution).
Note that I have CONFIG_DEVPTS_MULTIPLE_INSTANCES=y. It may be that
user space is doing something unusual, but it passes the test of
"works with 2.6.29, fails with 2.6.30".
I wasn't able to reproduce on an other system with a similar configuration.
Marc
next reply other threads:[~2009-05-08 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 21:54 Marc Dionne [this message]
2009-05-13 13:03 ` Geert Uytterhoeven
2009-05-13 17:15 ` Sukadev Bhattiprolu
2009-05-14 9:13 ` Geert Uytterhoeven
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=6041d2000905081454x4c9d8818oaccbcd14d1f4a506@mail.gmail.com \
--to=marc.c.dionne@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sukadev@linux.vnet.ibm.com \
/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
all inboxes | Powered by JetHome®