From: Wei Liu <wei.liu2@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 1/3] fuzz/x86emul: avoid race in link farm rune
Date: Mon, 20 Feb 2017 12:03:31 +0000 [thread overview]
Message-ID: <20170220120331.mc6rf34oc2wc4hqq@citrix.com> (raw)
In-Reply-To: <58A6F03D020000780013B432@prv-mh.provo.novell.com>
On Fri, Feb 17, 2017 at 04:44:45AM -0700, Jan Beulich wrote:
> >>> On 17.02.17 at 12:36, <wei.liu2@citrix.com> wrote:
> > On Fri, Feb 17, 2017 at 03:33:26AM -0700, Jan Beulich wrote:
> >> >>> On 17.02.17 at 11:12, <wei.liu2@citrix.com> wrote:
> >> > On Thu, Feb 16, 2017 at 07:10:41PM +0000, Andrew Cooper wrote:
> >> >> On 16/02/17 18:56, Wei Liu wrote:
> >> >> > --- a/tools/fuzz/x86_instruction_emulator/Makefile
> >> >> > +++ b/tools/fuzz/x86_instruction_emulator/Makefile
> >> >> > @@ -8,12 +8,16 @@ else
> >> >> > x86-instruction-emulator-fuzzer-all:
> >> >> > endif
> >> >> >
> >> >> > -x86_emulate/x86_emulate.c x86_emulate/x86_emulate.h:
> >> >> > +x86_emulate:
> >> >> > [ -L x86_emulate ] || ln -sf $(XEN_ROOT)/xen/arch/x86/x86_emulate .
> >> >> >
> >> >> > -asm/x86-vendors.h asm/x86-defns.h asm/msr-index.h:
> >> >> > +x86_emulate/x86_emulate.c x86_emulate/x86_emulate.h: x86_emulate
> >> >>
> >> >> You should be able to do this:
> >> >>
> >> >> x86_emulate/%: x86_emulate
> >> >>
> >> >
> >> > Using % won't work. Jan made a similar comment during the first
> >> > iteration of the fuzzer series. It turned out that we needed to list
> >> > explicitly every file because of the other rules explicitly listed
> >> > those files.
> >>
> >> There was something in that area, but explicitly mentioning files
> >> elsewhere should not prevent this dependency to work as long as
> >> the files don't exist without the rule's commands having run.
> >
> > I didn't dig out the old email so the description of the cause might be
> > inaccurate.
> >
> > Do you want me to do anything other than explicitly listing every file
> > as we did before? I'm not sure I get your request.
>
> Well, I'd prefer the shorter variant Andrew did suggest, so if that's
> not possible to be used here, I think it would help if the reason was
> recorded (in the commit message) now, to avoid later having the
> discussion yet another time.
I think I figure out how to make it work. New version of patches coming
soon.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-20 12:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 18:56 [PATCH 0/3] Fuzz/x86emual and x86emul/test fixes Wei Liu
2017-02-16 18:56 ` [PATCH 1/3] fuzz/x86emul: avoid race in link farm rune Wei Liu
2017-02-16 19:10 ` Andrew Cooper
2017-02-17 10:12 ` Wei Liu
2017-02-17 10:33 ` Jan Beulich
2017-02-17 11:36 ` Wei Liu
2017-02-17 11:44 ` Jan Beulich
2017-02-20 12:03 ` Wei Liu [this message]
2017-02-17 9:24 ` Jan Beulich
2017-02-17 10:12 ` Wei Liu
2017-02-16 18:56 ` [PATCH 2/3] x86emul/test: " Wei Liu
2017-02-16 18:56 ` [PATCH 3/3] gitignore: ignore asm soft link in fuzz and x86emul test Wei Liu
2017-02-17 9:24 ` Jan Beulich
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=20170220120331.mc6rf34oc2wc4hqq@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).