From: "Roman Yepishev" <roman.yepishev@gmail.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] UML crashes when built with _FORTIFY_SOURCE
Date: Mon, 3 Nov 2008 23:35:52 +0200 [thread overview]
Message-ID: <f39be10d0811031335me028b1dhed153cdbb956250@mail.gmail.com> (raw)
In-Reply-To: <20081031191452.GA10950@c2.user-mode-linux.org>
On Fri, Oct 31, 2008 at 9:14 PM, Jeff Dike <jdike@addtoit.com> wrote:
> On Sat, Oct 25, 2008 at 02:08:31AM +0300, Roman Yepishev wrote:
>> Temporary solution is to fix file declaration to be 108 or less bytes
>> but checks should be introduced when socket path is constructed.
>
> I don't really understand what you mean by checks being introduced,
> but how do you like the patch below?
>
> Jeff
>
> --
> Work email - jdike at linux dot intel dot com
>
[patch skipped]
Looks great, checked on i386 system - successfully builds and runs
with _FORTIFY_SOURCE.
By "checks" i meant the case when uml_dir and/or umid is too long to be used.
Currently the execution continues with a humble message
NET: Registered protocol family 1
>umid_file_name : buffer too short
Checking host MADV_REMOVE support...OK
Host TLS support detected
I guess this case should be documented somehow as well.
--
Regards,
Roman Yepishev
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2008-11-03 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 23:08 [uml-devel] UML crashes when built with _FORTIFY_SOURCE Roman Yepishev
2008-10-31 19:14 ` Jeff Dike
2008-11-03 21:35 ` Roman Yepishev [this message]
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=f39be10d0811031335me028b1dhed153cdbb956250@mail.gmail.com \
--to=roman.yepishev@gmail.com \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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