From: Joe Malicki <jmalicki@metacarta.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: chrisw@sous-sol.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH] CRED: Fix check_unsafe_exec()
Date: Tue, 17 Mar 2009 14:39:49 -0400 (EDT) [thread overview]
Message-ID: <14026175.11106541237315189656.JavaMail.root@ouachita> (raw)
In-Reply-To: <3830454.11106421237315019351.JavaMail.root@ouachita>
----- "Hugh Dickins" <hugh@veritas.com> wrote:
> On Thu, 12 Mar 2009, David Howells wrote:
> > Hugh Dickins <hugh@veritas.com> wrote:
> >
> > > We do. See the original thread. It's here at
> > > http://lkml.org/lkml/2009/2/26/233
> > > and appended below for convenience. We do know that patch did
> not
> > > fix Joe's problem, and we don't yet know whether addressing the
> > > files->count issue will actually fix it, but I'm hopeful.
> >
> > Looks reasonable.
>
> Thanks for taking a look.
>
> Yes, I'm inclined to go with that, and removing the files->count
> check from exec.c. Joe, did you manage to try your testing with
> my original patch plus that files->count check removed from 2.6.28's
> unsafe_exec()?
Sorry for not responding earlier.
I still got one failure with this new patch. I added some printks
to illuminate exactly why it's failing when it fails to setuid, but
of course, since adding the printks I haven't reproduced yet.
Very weird...
Thanks,
Joe
> Since Joe's bug has been around forever (if it is what we think it
> is), I'm disinclined to rush the fix - something nice to add to
> -stable, rather than needing to squeeze into 2.6.29.
>
> Hugh
>
next parent reply other threads:[~2009-03-17 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3830454.11106421237315019351.JavaMail.root@ouachita>
2009-03-17 18:39 ` Joe Malicki [this message]
2009-03-17 23:07 ` [PATCH] CRED: Fix check_unsafe_exec() Joe Malicki
2009-03-19 18:44 ` Hugh Dickins
[not found] <1906769.11304931237505721331.JavaMail.root@ouachita>
2009-03-19 23:36 ` Joe Malicki
2009-03-10 18:07 David Howells
2009-03-10 21:31 ` Hugh Dickins
2009-03-10 23:01 ` David Howells
2009-03-10 23:40 ` Hugh Dickins
2009-03-12 13:23 ` David Howells
2009-03-16 22:15 ` Hugh Dickins
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=14026175.11106541237315189656.JavaMail.root@ouachita \
--to=jmalicki@metacarta.com \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=dhowells@redhat.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox