All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler-SXC+2es9fhnfWeYVQQPykw@public.gmane.org>
To: Al Viro <viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
Cc: Linus Torvalds
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [git pull] gadgetfs fixes
Date: Sun, 15 Mar 2015 07:35:20 +0100	[thread overview]
Message-ID: <55052828.7090701@ahsoftware.de> (raw)
In-Reply-To: <20150315013948.GU29656-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>

Am 15.03.2015 um 02:39 schrieb Al Viro:
> On Sun, Mar 15, 2015 at 01:39:21AM +0100, Alexander Holler wrote:
>> Am 13.03.2015 um 17:42 schrieb Al Viro:
>>> 	Assorted fixes around AIO on gadgetfs: leaks, use-after-free,
>>> troubles caused by ->f_op flipping.  Please, pull from
>>> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git gadget
>>>
>>> Shortlog:
>>> Al Viro (8):
>>>       new helper: dup_iter()
>>>       move iov_iter.c from mm/ to lib/
>>>       gadget/function/f_fs.c: close leaks
>>>       gadget/function/f_fs.c: use put iov_iter into io_data
>>>       gadget/function/f_fs.c: switch to ->{read,write}_iter()
>>
>>>       gadgetfs: use-after-free in ->aio_read()
>>
>> If that patch ends up in the stable kernels (as it is marked as such),
>> it needs a
>> 	value = -ENOMEM
>> before that added "goto fail;", otherwise the return value is unitialized.
> 
> Umm...  If I'm not misparsing what you said, you are talking about the

Glücklicherweise nicht. Vielleicht sollten wir es zur Abwechslung mal
mit meiner bevorzugten Sprache versuchen.

> one that gets removed by
> -       if (iv) {
> -               priv->iv = kmemdup(iv, nr_segs * sizeof(struct iovec),
> -                                  GFP_KERNEL);
> -               if (!priv->iv) {
> -                       kfree(priv);
> -                       goto fail;
> -               }
> -       }
> in "gadget: switch ep_io_operations to ->read_iter/->write_iter" very
> shortly afterwards, and _that_ is a prereq for ->f_op flipping fixes,
> which is also clear -stable fodder.  But yes, it's a bisect hazard and
> a cherry-pick one as well.  Nice catch...

The following patches aren't marked for stable, otherwise I would not
have risked to become a victim of your comments again.

Alexander Holler
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Alexander Holler <holler@ahsoftware.de>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: [git pull] gadgetfs fixes
Date: Sun, 15 Mar 2015 07:35:20 +0100	[thread overview]
Message-ID: <55052828.7090701@ahsoftware.de> (raw)
In-Reply-To: <20150315013948.GU29656@ZenIV.linux.org.uk>

Am 15.03.2015 um 02:39 schrieb Al Viro:
> On Sun, Mar 15, 2015 at 01:39:21AM +0100, Alexander Holler wrote:
>> Am 13.03.2015 um 17:42 schrieb Al Viro:
>>> 	Assorted fixes around AIO on gadgetfs: leaks, use-after-free,
>>> troubles caused by ->f_op flipping.  Please, pull from
>>> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git gadget
>>>
>>> Shortlog:
>>> Al Viro (8):
>>>       new helper: dup_iter()
>>>       move iov_iter.c from mm/ to lib/
>>>       gadget/function/f_fs.c: close leaks
>>>       gadget/function/f_fs.c: use put iov_iter into io_data
>>>       gadget/function/f_fs.c: switch to ->{read,write}_iter()
>>
>>>       gadgetfs: use-after-free in ->aio_read()
>>
>> If that patch ends up in the stable kernels (as it is marked as such),
>> it needs a
>> 	value = -ENOMEM
>> before that added "goto fail;", otherwise the return value is unitialized.
> 
> Umm...  If I'm not misparsing what you said, you are talking about the

Glücklicherweise nicht. Vielleicht sollten wir es zur Abwechslung mal
mit meiner bevorzugten Sprache versuchen.

> one that gets removed by
> -       if (iv) {
> -               priv->iv = kmemdup(iv, nr_segs * sizeof(struct iovec),
> -                                  GFP_KERNEL);
> -               if (!priv->iv) {
> -                       kfree(priv);
> -                       goto fail;
> -               }
> -       }
> in "gadget: switch ep_io_operations to ->read_iter/->write_iter" very
> shortly afterwards, and _that_ is a prereq for ->f_op flipping fixes,
> which is also clear -stable fodder.  But yes, it's a bisect hazard and
> a cherry-pick one as well.  Nice catch...

The following patches aren't marked for stable, otherwise I would not
have risked to become a victim of your comments again.

Alexander Holler

  parent reply	other threads:[~2015-03-15  6:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 16:42 [git pull] gadgetfs fixes Al Viro
2015-03-15  0:39 ` Alexander Holler
2015-03-15  1:39   ` Al Viro
     [not found]     ` <20150315013948.GU29656-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2015-03-15  6:35       ` Alexander Holler [this message]
2015-03-15  6:35         ` Alexander Holler
2015-03-15  8:17         ` Al Viro
2015-03-15  8:31           ` Alexander Holler
2015-03-15  8:31             ` Alexander Holler
2015-03-16 10:11             ` Alexander Holler
2015-03-16 10:11               ` Alexander Holler
2015-03-15  8:50           ` Alexander Holler
2015-03-15  9:09             ` Al Viro

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=55052828.7090701@ahsoftware.de \
    --to=holler-sxc+2es9fhnfweyvqqpykw@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
    --cc=viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.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.