All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitri Monakhov <dmonakhov@openvz.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] prevent get_user_pages call from kernel thread
Date: Tue, 01 Jul 2008 13:36:09 +0400	[thread overview]
Message-ID: <m3prpyndyu.fsf@openvz.org> (raw)
In-Reply-To: <20080630133233.a3c2a4ef.akpm@linux-foundation.org> (Andrew Morton's message of "Mon\, 30 Jun 2008 13\:32\:33 -0700")

Andrew Morton <akpm@linux-foundation.org> writes:

> On Sun, 08 Jun 2008 19:37:32 +0400
> Dmitri Monakhov <dmonakhov@openvz.org> wrote:
>
>> Yes, yes.. everybody know that it is bad to write from kernel thread, and it
>> is madness to do it with O_DIRECT. But occasionally file with O_DIRECT flag
>> may be passed to loop device via LOOP_SET_FD. So if system hasn't address
>> space ops, or simply hide it like GFS, it is possible to kill kernel via
>> two lines program. In fact we can't effectively guard kernel space by
>> disabling O_DIRECT in loop's code, because user space can change it back
>> via fcntl(,F_SETFL,). Let's simply add sanity check mm related logic.
>> 
>> Signed-off-by: Dmitri Monakhov <dmonakhov@openvz.org>
>> ---
>>  drivers/block/loop.c |    1 +
>>  fs/direct-io.c       |    4 ++++
>>  2 files changed, 5 insertions(+), 0 deletions(-)
>> 
>> diff --git a/drivers/block/loop.c b/drivers/block/loop.c
>> index d3a25b0..bb2a262 100644
>> --- a/drivers/block/loop.c
>> +++ b/drivers/block/loop.c
>> @@ -753,6 +753,7 @@ static int loop_set_fd(struct loop_device *lo, struct file *lo_file,
>>  
>>  	mapping = file->f_mapping;
>>  	inode = mapping->host;
>> +	file->f_mode &= ~O_DIRECT;
>>  
>>  	if (!(file->f_mode & FMODE_WRITE))
>>  		lo_flags |= LO_FLAGS_READ_ONLY;
>> diff --git a/fs/direct-io.c b/fs/direct-io.c
>> index 9e81add..8e17224 100644
>> --- a/fs/direct-io.c
>> +++ b/fs/direct-io.c
>> @@ -149,6 +149,10 @@ static int dio_refill_pages(struct dio *dio)
>>  	int ret;
>>  	int nr_pages;
>>  
>> +	if (unlikely(!current->mm)) {
>> +		WARN_ON_ONCE(1);
>> +		return -EINVAL;
>> +	}
>>  	nr_pages = min(dio->total_pages - dio->curr_page, DIO_PAGES);
>>  	down_read(&current->mm->mmap_sem);
>>  	ret = get_user_pages(
>
> It's a bit rude to silently turn off O_DIRECT in this case.
>
> I think it would be better to simply fail the LOOP_SET_FD if the file
> has O_DIRECT and the relevant address_space_operations vectors are
> NULL.
Ok, i'll resend updated version, but we sill have to protect dio_defill_pages
against fcntl(,F_SETFL,) hack.

      reply	other threads:[~2008-07-01  9:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-08 15:37 [PATCH] prevent get_user_pages call from kernel thread Dmitri Monakhov
2008-06-30 20:32 ` Andrew Morton
2008-07-01  9:36   ` Dmitri Monakhov [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=m3prpyndyu.fsf@openvz.org \
    --to=dmonakhov@openvz.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 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.