All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Simon Horman <horms@verge.net.au>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Zhang Yanfei <zhangyanfei.yes@gmail.com>
Subject: Re: [PATCH 0/7] Remove unused /dev/oldmem interface
Date: Wed, 29 May 2013 12:10:20 -0400	[thread overview]
Message-ID: <20130529161020.GB22146@redhat.com> (raw)
In-Reply-To: <ec5cd077-c314-49d5-8970-439ffb9539fa@email.android.com>

On Tue, May 28, 2013 at 12:00:45PM -0700, Eric W. Biederman wrote:

[..]
> How can anyone use /dev/oldmem correctly?  To the best of
> my knowledge there are no parsers of the ELF header passed
> by /sbin/kexec in userspace.
> 
> If there is anyone who cares they can complain and we can
> revert the removal. All of the evidence is that everyone uses
> /proc/vmcore.
> 

Ok, that's fine. Given the fact that none of us has ever encountered
/dev/oldmem user, it is reasonably safe to remove it.

Thanks
Vivek

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Vivek Goyal <vgoyal@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Zhang Yanfei <zhangyanfei.yes@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Simon Horman <horms@verge.net.au>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/7] Remove unused /dev/oldmem interface
Date: Wed, 29 May 2013 12:10:20 -0400	[thread overview]
Message-ID: <20130529161020.GB22146@redhat.com> (raw)
In-Reply-To: <ec5cd077-c314-49d5-8970-439ffb9539fa@email.android.com>

On Tue, May 28, 2013 at 12:00:45PM -0700, Eric W. Biederman wrote:

[..]
> How can anyone use /dev/oldmem correctly?  To the best of
> my knowledge there are no parsers of the ELF header passed
> by /sbin/kexec in userspace.
> 
> If there is anyone who cares they can complain and we can
> revert the removal. All of the evidence is that everyone uses
> /proc/vmcore.
> 

Ok, that's fine. Given the fact that none of us has ever encountered
/dev/oldmem user, it is reasonably safe to remove it.

Thanks
Vivek

  reply	other threads:[~2013-05-29 16:10 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25  3:21 [PATCH 0/7] Remove unused /dev/oldmem interface Zhang Yanfei
2013-05-25  3:21 ` Zhang Yanfei
2013-05-25  3:24 ` [PATCH 1/7] /dev/oldmem: Remove the interface Zhang Yanfei
2013-05-25  3:24   ` Zhang Yanfei
2013-05-25  3:26 ` [PATCH 2/7] Documentation/devices.txt: Remove /dev/oldmem description Zhang Yanfei
2013-05-25  3:26   ` Zhang Yanfei
2013-05-25 23:20   ` Eric W. Biederman
2013-05-25 23:20     ` Eric W. Biederman
2013-05-26  0:58     ` Zhang Yanfei
2013-05-26  0:58       ` Zhang Yanfei
2013-05-27  1:27       ` HATAYAMA Daisuke
2013-05-27  1:27         ` HATAYAMA Daisuke
2013-05-27  1:27         ` Zhang Yanfei
2013-05-27  1:27           ` Zhang Yanfei
2013-05-29 22:20           ` Andrew Morton
2013-05-29 22:20             ` Andrew Morton
2013-05-30  5:49             ` Zhang Yanfei
2013-05-30  5:49               ` Zhang Yanfei
2013-05-25  3:27 ` [PATCH 3/7] Documentation/kdump/kdump.txt: " Zhang Yanfei
2013-05-25  3:27   ` Zhang Yanfei
2013-05-25  3:29 ` [PATCH 4/7] mips: Remove savemaxmem parameter setup Zhang Yanfei
2013-05-25  3:29   ` Zhang Yanfei
2013-05-25  3:31 ` [PATCH 5/7] powerpc: " Zhang Yanfei
2013-05-25  3:31   ` Zhang Yanfei
2013-05-25  3:33 ` [PATCH 6/7] ia64: Remove setting for saved_max_pfn Zhang Yanfei
2013-05-25  3:33   ` Zhang Yanfei
2013-05-25  3:36 ` [PATCH 7/7] s390: " Zhang Yanfei
2013-05-25  3:36   ` Zhang Yanfei
2013-05-25  7:11 ` [PATCH 0/7] Remove unused /dev/oldmem interface H. Peter Anvin
2013-05-25  7:11   ` H. Peter Anvin
2013-05-25 23:25 ` Eric W. Biederman
2013-05-25 23:25   ` Eric W. Biederman
2013-05-28 14:37   ` Vivek Goyal
2013-05-28 14:37     ` Vivek Goyal
2013-05-28 15:11     ` H. Peter Anvin
2013-05-28 15:11       ` H. Peter Anvin
2013-05-29 22:11       ` Andrew Morton
2013-05-29 22:11         ` Andrew Morton
2013-05-28 19:00     ` Eric W. Biederman
2013-05-28 19:00       ` Eric W. Biederman
2013-05-29 16:10       ` Vivek Goyal [this message]
2013-05-29 16:10         ` Vivek Goyal

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=20130529161020.GB22146@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=horms@verge.net.au \
    --cc=hpa@zytor.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhangyanfei.yes@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.