From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, Miklos Szeredi <mszeredi@suse.cz>
Subject: Re: [Bisected] commit 71574865 (vfs: do_last(): common slow lookup) breaks CUPS printing
Date: Mon, 30 Jul 2012 09:10:23 +0200 [thread overview]
Message-ID: <20120730071023.GA273@x4> (raw)
In-Reply-To: <20120730065046.GC6481@ZenIV.linux.org.uk>
On 2012.07.30 at 07:50 +0100, Al Viro wrote:
> On Sat, Jul 28, 2012 at 12:43:16PM +0200, Markus Trippelsdorf wrote:
> > Printing with CUPS is broken on the current git tree. Whenever I print a page
> > the job just sits in the CUPS queue showing "processing". But it never reaches
> > the printer. (My CUPS version is 1.5.2. Filesystem is xfs.)
> >
> > I've bisected this issue to:
> >
> > commit 7157486541bffc0dfec912e21ae639b029dae3d3
> > Author: Miklos Szeredi <mszeredi@suse.cz>
> > Date: Tue Jun 5 15:10:14 2012 +0200
> >
> > vfs: do_last(): common slow lookup
> >
> > Make the slow lookup part of O_CREAT and non-O_CREAT opens common.
> >
> > This allows atomic_open to be hooked into the slow lookup part.
> >
> > Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
> > Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
>
> Hmm... Looking at that commit, we seem to have one change introduced by it. Namely,
> behaviour of open(path, O_EXCL) (note that O_EXCL without O_CREAT is an undefined
> by POSIX and makes no damn sense anyway).
>
> Could you try the patch below, just to make sure that I'm not misreading the
> situation? If that's really happening that way, it should spew a warning,
> restore the old behaviour by removing that stray O_EXCL and, if it comes
> from open(2)/openat(2), print the syscall arguments.
>
> We'll need to restore the original behaviour anyway, undefined or no undefined,
> but if we really catch CUPS doing that, we ought to report that as a bug to
> whatever bugtracking system CUPS uses; at the very least, it's a portability
> headache waiting to happen.
Looks like you're right. The first warning happens during startup. The last one
when I print a test page (which now succeeds).
Thanks Al.
------------[ cut here ]------------
WARNING: at fs/open.c:899 do_sys_open+0x1e5/0x220()
Hardware name: System Product Name
Pid: 207, comm: X Not tainted 3.5.0-07078-gf7da9cd-dirty #199
Call Trace:
[<ffffffff810555a4>] ? warn_slowpath_common+0x74/0xb0
[<ffffffff810dd405>] ? do_sys_open+0x1e5/0x220
[<ffffffff814a64a2>] ? system_call_fastpath+0x16/0x1b
---[ end trace 9a333bfb6a9cbe80 ]---
------------[ cut here ]------------
WARNING: at fs/open.c:899 do_sys_open+0x1e5/0x220()
Hardware name: System Product Name
Pid: 384, comm: usb Tainted: G W 3.5.0-07078-gf7da9cd-dirty #199
Call Trace:
WTF: open("/dev/input/mice", 34946)
[<ffffffff810555a4>] ? warn_slowpath_common+0x74/0xb0
[<ffffffff810dd405>] ? do_sys_open+0x1e5/0x220
[<ffffffff814a64a2>] ? system_call_fastpath+0x16/0x1b
---[ end trace 9a333bfb6a9cbe81 ]---
WTF: open("/dev/usblp0", 32898)
------------[ cut here ]------------
WARNING: at fs/open.c:899 do_sys_open+0x1e5/0x220()
Hardware name: System Product Name
Pid: 384, comm: usb Tainted: G W 3.5.0-07078-gf7da9cd-dirty #199
Call Trace:
[<ffffffff810555a4>] ? warn_slowpath_common+0x74/0xb0
[<ffffffff810dd405>] ? do_sys_open+0x1e5/0x220
[<ffffffff814a64a2>] ? system_call_fastpath+0x16/0x1b
---[ end trace 9a333bfb6a9cbe82 ]---
------------[ cut here ]------------
WARNING: at fs/open.c:899 do_sys_open+0x1e5/0x220()
Hardware name: System Product Name
Pid: 87, comm: cupsd Tainted: G W 3.5.0-07078-gf7da9cd-dirty #199
Call Trace:
WTF: open("/dev/usb/lp0", 32898)
[<ffffffff810555a4>] ? warn_slowpath_common+0x74/0xb0
[<ffffffff810dd405>] ? do_sys_open+0x1e5/0x220
[<ffffffff814a64a2>] ? system_call_fastpath+0x16/0x1b
---[ end trace 9a333bfb6a9cbe83 ]---
--
Markus
next prev parent reply other threads:[~2012-07-30 7:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-28 10:43 [Bisected] commit 71574865 (vfs: do_last(): common slow lookup) breaks CUPS printing Markus Trippelsdorf
2012-07-30 6:50 ` Al Viro
2012-07-30 7:10 ` Markus Trippelsdorf [this message]
2012-07-30 7:56 ` Al Viro
2012-07-30 8:05 ` Markus Trippelsdorf
2012-07-30 8:26 ` Al Viro
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=20120730071023.GA273@x4 \
--to=markus@trippelsdorf.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@suse.cz \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.