From: Andi Kleen <andi@firstfloor.org>
To: Daisuke HATAYAMA <d.hatayama@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
jdike@addtoit.com, tony.luck@intel.com, mhiramat@redhat.com
Subject: Re: [RFC, PATCH 3/4] elf_core_dump(): make offset calculation and writing processes explicit
Date: Tue, 15 Dec 2009 15:07:31 +0100 [thread overview]
Message-ID: <87ocm0wct8.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20091215.114137.104035145.d.hatayama@jp.fujitsu.com> (Daisuke HATAYAMA's message of "Tue, 15 Dec 2009 11:41:37 +0900 (JST)")
Daisuke HATAYAMA <d.hatayama@jp.fujitsu.com> writes:
>
> However, the clause 1. is not always possible, since one
> cannot assume that dump_seek() function always supports
> the seek in the minus direction. Consider no_llseek.
Not even forward seek is always supported, consider core dumping
to a pipe.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-12-15 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 2:41 [RFC, PATCH 3/4] elf_core_dump(): make offset calculation and writing processes explicit Daisuke HATAYAMA
2009-12-15 14:07 ` Andi Kleen [this message]
2009-12-16 2:27 ` Daisuke HATAYAMA
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=87ocm0wct8.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=d.hatayama@jp.fujitsu.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=tony.luck@intel.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