The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, jfs-discussion@lists.sourceforge.net
Subject: Re: [Jfs-discussion] [PATCH 5/6] fs/jfs: Add printf format/argument verification
Date: Thu, 11 Nov 2010 09:31:41 -0600	[thread overview]
Message-ID: <1289489501.6848.13.camel@shaggy-w500> (raw)
In-Reply-To: <a22ba4f754931aabc3928435e613a1b809d31f9e.1289432524.git.joe@perches.com>

On Wed, 2010-11-10 at 15:46 -0800, Joe Perches wrote:
> Add __attribute__((format... to jfs_error.
> 
> All arguments matched formats, no other changes necessary.
> 
> Signed-off-by: Joe Perches <joe@perches.com>

Acked-by: Dave Kleikamp <shaggy@linux.vnet.ibm.com>

Would you like to push this patchset as a group, or would you like me to
push this patch through the jfs tree?

Shaggy

> ---
>  fs/jfs/jfs_superblock.h |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/fs/jfs/jfs_superblock.h b/fs/jfs/jfs_superblock.h
> index 884fc21..1da2538 100644
> --- a/fs/jfs/jfs_superblock.h
> +++ b/fs/jfs/jfs_superblock.h
> @@ -108,6 +108,8 @@ struct jfs_superblock {
> 
>  extern int readSuper(struct super_block *, struct buffer_head **);
>  extern int updateSuper(struct super_block *, uint);
> +
> +__attribute__((format(printf, 2, 3)))
>  extern void jfs_error(struct super_block *, const char *, ...);
>  extern int jfs_mount(struct super_block *);
>  extern int jfs_mount_rw(struct super_block *, int);

-- 
Dave Kleikamp
IBM Linux Technology Center


  reply	other threads:[~2010-11-11 15:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 23:46 [PATCH 0/6] fs: Add printf format/argument verification Joe Perches
2010-11-10 23:46 ` [PATCH 1/6] fs/adfs: Add printf format/argument verification and fix fallout Joe Perches
2010-11-10 23:46 ` [PATCH 2/6] fs/affs: " Joe Perches
2010-11-11  9:20   ` Geert Uytterhoeven
2010-11-11 10:14     ` [PATCH] fs/affs/file.c: Use appropriate format types and casts Joe Perches
2010-11-10 23:46 ` [PATCH 3/6] fs/befs: Add printf format/argument verification and fix fallout Joe Perches
2010-11-10 23:46 ` [PATCH 4/6] fs/ecryptfs: " Joe Perches
2010-11-16  3:28   ` Tyler Hicks
2010-11-10 23:46 ` [PATCH 5/6] fs/jfs: Add printf format/argument verification Joe Perches
2010-11-11 15:31   ` Dave Kleikamp [this message]
2010-11-12  8:53     ` [Jfs-discussion] " Joe Perches
2010-11-10 23:46 ` [PATCH 6/6] fs/udf: " Joe Perches
2010-11-11  9:55   ` Jan Kara

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=1289489501.6848.13.camel@shaggy-w500 \
    --to=shaggy@linux.vnet.ibm.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=joe@perches.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