From: Peter Oberparleiter seq_write() can be used to construct seq_files containing arbitrary data. Required by the gcov-profiling interface to synthesize binary profiling data files. Signed-off-by: Peter Oberparleiter Cc: Al Viro --- fs/seq_file.c | 20 ++++++++++++++++++++ include/linux/seq_file.h | 1 + 2 files changed, 21 insertions(+) Index: linux-2.6.30-rc6/fs/seq_file.c =================================================================== --- linux-2.6.30-rc6.orig/fs/seq_file.c 2009-05-19 12:27:37.000000000 +0200 +++ linux-2.6.30-rc6/fs/seq_file.c 2009-05-19 12:41:26.000000000 +0200 @@ -640,6 +640,26 @@ } EXPORT_SYMBOL(seq_puts); +/** + * seq_write - write arbitrary data to buffer + * @seq: seq_file identifying the buffer to which data should be written + * @data: data address + * @len: number of bytes + * + * Return 0 on success, non-zero otherwise. + */ +int seq_write(struct seq_file *seq, const void *data, size_t len) +{ + if (seq->count + len < seq->size) { + memcpy(seq->buf + seq->count, data, len); + seq->count += len; + return 0; + } + seq->count = seq->size; + return -1; +} +EXPORT_SYMBOL(seq_write); + struct list_head *seq_list_start(struct list_head *head, loff_t pos) { struct list_head *lh; Index: linux-2.6.30-rc6/include/linux/seq_file.h =================================================================== --- linux-2.6.30-rc6.orig/include/linux/seq_file.h 2009-05-19 12:27:37.000000000 +0200 +++ linux-2.6.30-rc6/include/linux/seq_file.h 2009-05-19 12:41:26.000000000 +0200 @@ -43,6 +43,7 @@ int seq_escape(struct seq_file *, const char *, const char *); int seq_putc(struct seq_file *m, char c); int seq_puts(struct seq_file *m, const char *s); +int seq_write(struct seq_file *seq, const void *data, size_t len); int seq_printf(struct seq_file *, const char *, ...) __attribute__ ((format (printf,2,3))); -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/