mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alex Polvi" <polvi@google.com>
To: "Trond Myklebust" <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sunrpc/auth_gss: NULL pointer deref in gss_pipe_release()
Date: Tue, 1 Aug 2006 21:10:08 -0400	[thread overview]
Message-ID: <e561bacc0608011810r1313a361h28263b2fa0bf876e@mail.google.com> (raw)
In-Reply-To: <1154378242.13744.14.camel@localhost>

On 7/31/06, Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> On Mon, 2006-07-31 at 10:50 -0400, Alex Polvi wrote:
> > Proposed (trivial) patch to fix a NULL pointer deref in
> > gss_pipe_release(). While this does seem to fix the problem, I'm not
> > entirely sure it is the correct place to handle the NULL pointer.
> >
> > Included below is the script I used to recreate the problem, the oops,
> > and the patch.
>
> Sorry, but that is not the correct fix. The problem here is rather that
> something is causing us to call rpc_close_pipes() on the file after the
> call to gss_destroy(). That is supposed to be illegal.

Would you be willing to explain what should happen? I.e. what is the
lifecycle of an RPC inode?

Thanks,

-Alex

  reply	other threads:[~2006-08-02  1:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31 14:50 Alex Polvi
2006-07-31 20:37 ` Trond Myklebust
2006-08-02  1:10   ` Alex Polvi [this message]
2006-08-09  2:58   ` Alex Polvi
2006-08-09 15:27   ` [PATCHv2] " Alex Polvi
2006-08-09 15:39     ` Trond Myklebust
2006-08-14 19:32       ` [PATCHv3] " Alex Polvi
2006-08-14 20:34         ` Alex Polvi
2006-08-14 22:46           ` Trond Myklebust
2006-08-15  0:09             ` Alex Polvi

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=e561bacc0608011810r1313a361h28263b2fa0bf876e@mail.google.com \
    --to=polvi@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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
all inboxes | Powered by JetHome®