linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabian Frederick <fabf@skynet.be>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 1/1 linux-next] affs: add default case in switch
Date: Sun, 3 May 2015 20:15:50 +0200 (CEST)	[thread overview]
Message-ID: <1190129389.190434.1430676950131.open-xchange@webmail.nmp.proximus.be> (raw)
In-Reply-To: <CAFLxGvyLsnus_OLX4x6bjtHEoHUESqdpfQpaXLVeKub-dL1s+Q@mail.gmail.com>



> On 03 May 2015 at 16:51 Richard Weinberger <richard.weinberger@gmail.com>
> wrote:
>
>
> On Sat, May 2, 2015 at 8:56 PM, Fabian Frederick <fabf@skynet.be> wrote:
> > Fix gcc -Wswitch-default warnings
> >
> > Cc: Andrew Morton <akpm@linux-foundation.org>
> > Signed-off-by: Fabian Frederick <fabf@skynet.be>
> > ---
> >  fs/affs/inode.c | 2 ++
> >  fs/affs/namei.c | 3 +++
> >  2 files changed, 5 insertions(+)
> >
> > diff --git a/fs/affs/inode.c b/fs/affs/inode.c
> > index 1734950..623398e 100644
> > --- a/fs/affs/inode.c
> > +++ b/fs/affs/inode.c
> > @@ -143,6 +143,8 @@ struct inode *affs_iget(struct super_block *sb, unsigned
> > long ino)
> >                 inode->i_op = &affs_symlink_inode_operations;
> >                 inode->i_data.a_ops = &affs_symlink_aops;
> >                 break;
> > +       default:
> > +               break;
> >         }
> >
> >         inode->i_mtime.tv_sec = inode->i_atime.tv_sec =
> >inode->i_ctime.tv_sec
> > diff --git a/fs/affs/namei.c b/fs/affs/namei.c
> > index 181e05b..517926d 100644
> > --- a/fs/affs/namei.c
> > +++ b/fs/affs/namei.c
> > @@ -237,6 +237,9 @@ affs_lookup(struct inode *dir, struct dentry *dentry,
> > unsigned int flags)
> >                 //case ST_LINKDIR:
> >                 case ST_LINKFILE:
> >                         ino = be32_to_cpu(AFFS_TAIL(sb, bh)->original);
> > +                       break;
> > +               default:
> > +                       break;
>
> How can this code path be reached?
> If I read your patch correctly it just silences gcc.
>
> If the code can be reached you need to take a proper action of not the
> warning is bogus.

As far as I understand, switch in affs_lookup() only updates inode number when
it's a link so we can simply add default:break to silence gcc warning or replace
by if().

affs_iget() switch on the other hand applies to any type of file.
Maybe we could add default: BUG() to avoid working on bad inode ?

Regards,
Fabian
>
> --
> Thanks,
> //richard
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-05-03 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-02 18:56 [PATCH 1/1 linux-next] affs: add default case in switch Fabian Frederick
2015-05-03 14:51 ` Richard Weinberger
2015-05-03 18:15   ` Fabian Frederick [this message]
2015-05-03 18:23     ` Richard Weinberger
2015-05-03 18:38       ` Fabian Frederick
2015-05-03 18:39         ` Richard Weinberger

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=1190129389.190434.1430676950131.open-xchange@webmail.nmp.proximus.be \
    --to=fabf@skynet.be \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@gmail.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;
as well as URLs for NNTP newsgroup(s).