From: Tim Pepper <lnxninja@linux.vnet.ibm.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Tim Pepper <lnxninja@linux.vnet.ibm.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lockdep: Avoid /proc/lockdep & lock_stat infinite output
Date: Mon, 8 Oct 2007 21:04:02 -0700 [thread overview]
Message-ID: <20071009040401.GA3493@tpepper-t42p.dolavim.us> (raw)
In-Reply-To: <20071009013011.GV8181@ftp.linux.org.uk>
On Tue 09 Oct at 02:30:11 +0100 viro@ftp.linux.org.uk said:
> On Mon, Oct 08, 2007 at 06:15:51PM -0700, Tim Pepper wrote:
> >
> > - if (&class->lock_entry == all_lock_classes.next)
> > + if (*pos == 0)
> > seq_printf(m, "all lock classes:\n");
>
> Do not generate output outside of ->show() and you won't have these
> problems. That's where your infinite output crap comes from.
>
> IOW, NAK - fix the underlying problem.
Aaah...OK. Can we add something like the following then:
Document that output must only come from _show() and SEQ_START_TOKEN is how
a _start() indicates a header is to be printed.
Signed-off-by: Tim Pepper <lnxninja@linux.vnet.ibm.com>
Cc: Al Viro <viro@ftp.linux.org.uk>
---
--- linux-2.6.orig/include/linux/seq_file.h
+++ linux-2.6.23-rc9/include/linux/seq_file.h
@@ -36,9 +36,10 @@ ssize_t seq_read(struct file *, char __u
loff_t seq_lseek(struct file *, loff_t, int);
int seq_release(struct inode *, struct file *);
int seq_escape(struct seq_file *, const char *, const char *);
+
+/* these may only be called from a (*show) function */
int seq_putc(struct seq_file *m, char c);
int seq_puts(struct seq_file *m, const char *s);
-
int seq_printf(struct seq_file *, const char *, ...)
__attribute__ ((format (printf,2,3)));
@@ -48,6 +49,11 @@ int single_open(struct file *, int (*)(s
int single_release(struct inode *, struct file *);
int seq_release_private(struct inode *, struct file *);
+/*
+ * return SEQ_START_TOKEN in your (*start) function and test for
+ * (v == SEQ_START_TOKEN) in * your (*show) funtion in order to
+ * print a header before your seq data
+ */
#define SEQ_START_TOKEN ((void *)1)
/*
next prev parent reply other threads:[~2007-10-09 4:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 1:15 Tim Pepper
2007-10-09 1:30 ` Al Viro
2007-10-09 4:04 ` Tim Pepper [this message]
2007-10-09 11:14 ` Peter Zijlstra
2007-10-09 22:10 ` Tim Pepper
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=20071009040401.GA3493@tpepper-t42p.dolavim.us \
--to=lnxninja@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=viro@ftp.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 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®