linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Khlebnikov <koct9i@gmail.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH RFC] proc/pid/mem: implement SEEK_DATA and SEEK_HOLE
Date: Sat, 24 May 2014 17:50:35 +0400	[thread overview]
Message-ID: <20140524135035.32281.93663.stgit@zurg> (raw)

lseek(fd, addr, SEEK_DATA) adjust file offset to the start address of next VMA,
or to addr if this address is allocated.

lseek(fd, addr, SEEK_HOLE) adjust file offset to the end address of VMA which
addr belongs to, or to addr itself if there is hole.

This way SEEK_HOLE reports a virtual zero-length hole between each contiguous
VMAs. This hack seems completely legit and allows to simplify implementation
(there is no function for finding next hole in VMAs' tree, walking along
 ->vm_next might be expensive) This also gives more information about layout.

Signed-off-by: Konstantin Khlebnikov <koct9i@gmail.com>

---

I have no practical use for this, just found this interesting.
---
 fs/proc/base.c |   31 +++++++++++++++++++++++++++++--
 1 file changed, 29 insertions(+), 2 deletions(-)

diff --git a/fs/proc/base.c b/fs/proc/base.c
index 2d696b0..aba4b47 100644
--- a/fs/proc/base.c
+++ b/fs/proc/base.c
@@ -769,13 +769,40 @@ static ssize_t mem_write(struct file *file, const char __user *buf,
 
 loff_t mem_lseek(struct file *file, loff_t offset, int orig)
 {
+	struct mm_struct *mm = file->private_data;
+	struct vm_area_struct *vma;
+
 	switch (orig) {
-	case 0:
+	case SEEK_SET:
 		file->f_pos = offset;
 		break;
-	case 1:
+	case SEEK_CUR:
 		file->f_pos += offset;
 		break;
+	case SEEK_DATA:
+	case SEEK_HOLE:
+		if (!mm || !atomic_inc_not_zero(&mm->mm_users))
+			return -ENXIO;
+		down_read(&mm->mmap_sem);
+		vma = find_vma(mm, offset);
+		if (vma) {
+			if (orig == SEEK_DATA) {
+				if (offset >= vma->vm_start)
+					file->f_pos = offset;
+				else
+					file->f_pos = vma->vm_start;
+			} else {
+				if (offset < vma->vm_start)
+					file->f_pos = offset;
+				else
+					file->f_pos = vma->vm_end;
+			}
+		}
+		up_read(&mm->mmap_sem);
+		mmput(mm);
+		if (!vma)
+			return -ENXIO;
+		break;
 	default:
 		return -EINVAL;
 	}

--
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>

                 reply	other threads:[~2014-05-24 13:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140524135035.32281.93663.stgit@zurg \
    --to=koct9i@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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).