From: Al Viro <viro@ftp.linux.org.uk>
To: Robin Holt <holt@sgi.com>
Cc: Dean Nelson <dcn@sgi.com>,
akpm@linux-foundation.org, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
tony.luck@intel.com, jes@sgi.com
Subject: Re: [PATCH 1/4] export __put_task_struct for XPMEM
Date: Mon, 27 Aug 2007 20:47:52 +0000 [thread overview]
Message-ID: <20070827204752.GK21089@ftp.linux.org.uk> (raw)
In-Reply-To: <20070827202420.GE22922@lnx-holt.americas.sgi.com>
On Mon, Aug 27, 2007 at 03:24:20PM -0500, Robin Holt wrote:
> On Mon, Aug 27, 2007 at 08:35:10PM +0100, Al Viro wrote:
> > On Mon, Aug 27, 2007 at 02:19:06PM -0500, Dean Nelson wrote:
> >
> > > No operations can be done once it's closed, only while it's opened.
> >
> > What the hell do you mean, can't be done?
> >
> > fd = open(...);
> > fp = popen("/bin/date", "r");
> > /* read from fp */
> > fclose(fp);
>
> But this will operate on the dup'd fd. We detect that in the flush
> (ignore) and ioctl (return errors) operations. All other operations
> are not handled by xpmem.
How the hell do you detect dup'd fd? It's identical to the original
in every respect and it doesn't have to be held by a different task.
Seriously, what you are proposing makes no sense whatsoever...
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ftp.linux.org.uk>
To: Robin Holt <holt@sgi.com>
Cc: Dean Nelson <dcn@sgi.com>,
akpm@linux-foundation.org, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
tony.luck@intel.com, jes@sgi.com
Subject: Re: [PATCH 1/4] export __put_task_struct for XPMEM
Date: Mon, 27 Aug 2007 21:47:52 +0100 [thread overview]
Message-ID: <20070827204752.GK21089@ftp.linux.org.uk> (raw)
In-Reply-To: <20070827202420.GE22922@lnx-holt.americas.sgi.com>
On Mon, Aug 27, 2007 at 03:24:20PM -0500, Robin Holt wrote:
> On Mon, Aug 27, 2007 at 08:35:10PM +0100, Al Viro wrote:
> > On Mon, Aug 27, 2007 at 02:19:06PM -0500, Dean Nelson wrote:
> >
> > > No operations can be done once it's closed, only while it's opened.
> >
> > What the hell do you mean, can't be done?
> >
> > fd = open(...);
> > fp = popen("/bin/date", "r");
> > /* read from fp */
> > fclose(fp);
>
> But this will operate on the dup'd fd. We detect that in the flush
> (ignore) and ioctl (return errors) operations. All other operations
> are not handled by xpmem.
How the hell do you detect dup'd fd? It's identical to the original
in every respect and it doesn't have to be held by a different task.
Seriously, what you are proposing makes no sense whatsoever...
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ftp.linux.org.uk>
To: Robin Holt <holt@sgi.com>
Cc: Dean Nelson <dcn@sgi.com>,
akpm@linux-foundation.org, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
tony.luck@intel.com, jes@sgi.com
Subject: Re: [PATCH 1/4] export __put_task_struct for XPMEM
Date: Mon, 27 Aug 2007 21:47:52 +0100 [thread overview]
Message-ID: <20070827204752.GK21089@ftp.linux.org.uk> (raw)
In-Reply-To: <20070827202420.GE22922@lnx-holt.americas.sgi.com>
On Mon, Aug 27, 2007 at 03:24:20PM -0500, Robin Holt wrote:
> On Mon, Aug 27, 2007 at 08:35:10PM +0100, Al Viro wrote:
> > On Mon, Aug 27, 2007 at 02:19:06PM -0500, Dean Nelson wrote:
> >
> > > No operations can be done once it's closed, only while it's opened.
> >
> > What the hell do you mean, can't be done?
> >
> > fd = open(...);
> > fp = popen("/bin/date", "r");
> > /* read from fp */
> > fclose(fp);
>
> But this will operate on the dup'd fd. We detect that in the flush
> (ignore) and ioctl (return errors) operations. All other operations
> are not handled by xpmem.
How the hell do you detect dup'd fd? It's identical to the original
in every respect and it doesn't have to be held by a different task.
Seriously, what you are proposing makes no sense whatsoever...
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-08-27 20:47 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 15:56 [PATCH 0/4] SGI Altix cross partition memory (XPMEM) Dean Nelson
2007-08-27 15:56 ` Dean Nelson
2007-08-27 15:56 ` Dean Nelson
2007-08-27 15:59 ` [PATCH 1/4] export __put_task_struct for XPMEM Dean Nelson
2007-08-27 15:59 ` Dean Nelson
2007-08-27 15:59 ` Dean Nelson
2007-08-27 16:13 ` Al Viro
2007-08-27 16:13 ` Al Viro
2007-08-27 16:13 ` Al Viro
2007-08-27 18:10 ` Dean Nelson
2007-08-27 18:10 ` Dean Nelson
2007-08-27 18:10 ` Dean Nelson
2007-08-27 18:15 ` Al Viro
2007-08-27 18:15 ` Al Viro
2007-08-27 18:15 ` Al Viro
2007-08-27 19:19 ` Dean Nelson
2007-08-27 19:19 ` Dean Nelson
2007-08-27 19:19 ` Dean Nelson
2007-08-27 19:35 ` Al Viro
2007-08-27 19:35 ` Al Viro
2007-08-27 19:35 ` Al Viro
2007-08-27 20:24 ` Robin Holt
2007-08-27 20:24 ` Robin Holt
2007-08-27 20:24 ` Robin Holt
2007-08-27 20:47 ` Al Viro [this message]
2007-08-27 20:47 ` Al Viro
2007-08-27 20:47 ` Al Viro
2007-08-28 12:09 ` Robin Holt
2007-08-28 18:01 ` Christoph Hellwig
2007-08-28 18:01 ` Christoph Hellwig
2007-08-28 18:01 ` Christoph Hellwig
2007-08-27 16:01 ` [PATCH 2/4] export zap_page_range " Dean Nelson
2007-08-27 16:01 ` Dean Nelson
2007-08-27 16:01 ` Dean Nelson
2007-08-27 16:02 ` [PATCH 3/4] add new lock ordering rule to mm/filemap.c Dean Nelson
2007-08-27 16:02 ` Dean Nelson
2007-08-27 16:02 ` Dean Nelson
2007-08-27 16:41 ` [PATCH 4/4] add SGI Altix cross partition memory (XPMEM) driver Dean Nelson
2007-08-27 16:41 ` Dean Nelson
2007-08-27 20:00 ` Adrian Bunk
2007-08-27 20:00 ` Adrian Bunk
2007-08-27 20:00 ` Adrian Bunk
2007-08-28 18:02 ` Christoph Hellwig
2007-08-28 18:02 ` Christoph Hellwig
2007-08-28 18:02 ` Christoph Hellwig
2007-08-28 19:00 ` Robin Holt
2007-08-28 19:00 ` Robin Holt
2007-08-28 19:00 ` Robin Holt
2007-08-28 19:05 ` Christoph Hellwig
2007-08-28 19:05 ` Christoph Hellwig
2007-08-28 19:05 ` Christoph Hellwig
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=20070827204752.GK21089@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=dcn@sgi.com \
--cc=holt@sgi.com \
--cc=jes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 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.