From: Sasha Levin <sasha.levin@oracle.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@ZenIV.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
akpm@linux-foundation.org
Subject: Re: [PATCH] autofs4: check dev ioctl size before allocating
Date: Sat, 05 Apr 2014 23:11:03 -0400 [thread overview]
Message-ID: <5340C5C7.9010203@oracle.com> (raw)
In-Reply-To: <1396753403.24991.3.camel@perseus.fritz.box>
On 04/05/2014 11:03 PM, Ian Kent wrote:
> On Sat, 2014-04-05 at 11:06 -0400, Sasha Levin wrote:
>> Ping? Anyone wants to take this?
>
> Is this causing a problem for users?
> If it is I'll send it to Andrew straight away.
>
> I do have this on my queue but don't have any other patches to send so
> it's just sitting there.
>
> If it worries you I'll send it to Andrew now.
It's not really a pressing issue since /dev/autofs is accessible only to
root. I also doubt that it causes problems for actual users.
If there are no issues with the patch, I think it's best if you could
ack/sign off on it and if Andrew wants to take it now, he could. If he
doesn't, it could wait for whenever.
I just don't want it getting lost somewhere and never making it upstream.
Thanks,
Sasha
next prev parent reply other threads:[~2014-04-06 3:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 1:40 [PATCH] autofs4: check dev ioctl size before allocating Sasha Levin
2014-04-05 15:06 ` Sasha Levin
2014-04-06 3:03 ` Ian Kent
2014-04-06 3:11 ` Sasha Levin [this message]
2014-04-06 3:53 ` Ian Kent
2014-04-07 0:03 ` Sasha Levin
-- strict thread matches above, loose matches on Subject: below --
2014-04-07 1:42 Ian Kent
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=5340C5C7.9010203@oracle.com \
--to=sasha.levin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=autofs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=viro@ZenIV.linux.org.uk \
/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.