From: Peter Maydell <peter.maydell@linaro.org>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: Blue Swirl <blauwirbel@gmail.com>,
Riku Voipio <riku.voipio@iki.fi>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] linux-user: fix emulation of getdents
Date: Mon, 20 Aug 2012 23:05:40 +0100 [thread overview]
Message-ID: <CAFEAcA-W1+qBTT-FCT-9YkZyyhNvPTBoD4x3TU_EE-cpSy5MWw@mail.gmail.com> (raw)
In-Reply-To: <20120820213617.GA22459@altlinux.org>
On 20 August 2012 22:36, Dmitry V. Levin <ldv@altlinux.org> wrote:
> In case when TARGET_ABI_BITS == 32 && HOST_LONG_BITS == 64, the last
> byte of the target dirent structure (aka d_type byte) was never copied
> from the host dirent structure, thus breaking everything that relies
> on valid d_type value, e.g. glob(3).
Looks pretty good, just one nit...
> diff --git a/linux-user/syscall_defs.h b/linux-user/syscall_defs.h
> index 2cfda5a..f7271fa 100644
> --- a/linux-user/syscall_defs.h
> +++ b/linux-user/syscall_defs.h
> @@ -258,7 +258,7 @@ struct target_dirent {
> abi_long d_ino;
> abi_long d_off;
> unsigned short d_reclen;
> - char d_name[256]; /* We must not include limits.h! */
> + char d_name[];
> };
Can you convert this struct to match coding style while you're touching
it, please? (ie no hardcoded tabs). scripts/checkpatch.pl will let you
know about this kind of thing.
thanks
-- PMM
next prev parent reply other threads:[~2012-08-20 22:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 21:20 [Qemu-devel] [PATCH] linux-user: fix emulation of getdents Dmitry V. Levin
2012-08-17 7:33 ` 陳韋任 (Wei-Ren Chen)
2012-08-18 14:20 ` Blue Swirl
2012-08-18 21:56 ` [Qemu-devel] [PATCH v2] " Dmitry V. Levin
2012-08-19 12:59 ` Blue Swirl
2012-08-20 16:17 ` Peter Maydell
2012-08-20 21:36 ` [Qemu-devel] [PATCH v3] " Dmitry V. Levin
2012-08-20 22:05 ` Peter Maydell [this message]
2012-08-20 22:13 ` [Qemu-devel] [PATCH v4] " Dmitry V. Levin
2012-08-21 12:03 ` Peter Maydell
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=CAFEAcA-W1+qBTT-FCT-9YkZyyhNvPTBoD4x3TU_EE-cpSy5MWw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=blauwirbel@gmail.com \
--cc=ldv@altlinux.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).