From: David Laight <David.Laight@ACULAB.COM>
To: 'Quentin Monnet' <quentin.monnet@netronome.com>,
"ast@kernel.org" <ast@kernel.org>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"kafai@fb.com" <kafai@fb.com>,
"songliubraving@fb.com" <songliubraving@fb.com>,
"yhs@fb.com" <yhs@fb.com>,
"jakub.kicinski@netronome.com" <jakub.kicinski@netronome.com>,
"df@google.com" <df@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] bpf: bpftool: convert ‘const char *’ type into 'char *' in assignment
Date: Thu, 28 Mar 2019 15:08:49 +0000 [thread overview]
Message-ID: <ebf3f6b747cb4400b8357e361b1f522a@AcuMS.aculab.com> (raw)
In-Reply-To: <d870f83e-48fa-7372-7664-e268aa1acf6c@netronome.com>
From: Quentin Monnet
> Sent: 28 March 2019 14:31
> 2019-03-28 10:16 UTC-0400 ~ Bo YU <tsu.yubo@gmail.com>
> > When compiling with check flag: make -C tools/bpf/bpftool/
> > gcc will warning:
> >
> > jit_disasm.c:119:29: warning: assignment discards ‘const’ qualifier from
> > pointer target type [-Wdiscarded-qualifiers]
> > info.disassembler_options = disassembler_options;
> >
> > So convert 'const char *' type into 'char *' to fix the warning.
> >
...
> > --- a/tools/bpf/bpftool/jit_disasm.c
> > +++ b/tools/bpf/bpftool/jit_disasm.c
> > @@ -116,7 +116,7 @@ void disasm_print_insn(unsigned char *image, ssize_t
> > len, int opcodes,
> > info.arch = bfd_get_arch(bfdf);
> > info.mach = bfd_get_mach(bfdf);
> > if (disassembler_options)
> > - info.disassembler_options = disassembler_options;
> > + info.disassembler_options = (char *)disassembler_options;
> > info.buffer = image;
> > info.buffer_length = len;
At some point someone may decide to build with -Wcast-const
at which point you've just generated a different error.
The (probably) correct fix is to make info.disassempler_options 'const char *'.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2019-03-28 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 14:16 [PATCH] bpf: bpftool: convert ‘const char *’ type into 'char *' in assignment Bo YU
2019-03-28 14:30 ` Quentin Monnet
2019-03-28 14:38 ` Bo YU
2019-03-28 15:08 ` David Laight [this message]
2019-03-28 15:58 ` Quentin Monnet
2019-03-28 14:36 ` Mukesh Ojha
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=ebf3f6b747cb4400b8357e361b1f522a@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=df@google.com \
--cc=jakub.kicinski@netronome.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=quentin.monnet@netronome.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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).