LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Andrey Vagin <avagin@openvz.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: Correctly check d_alloc_name() return code in devpts_pty_new
Date: Thu, 3 Feb 2011 07:56:12 -0800	[thread overview]
Message-ID: <20110203155612.GA983@suse.de> (raw)
In-Reply-To: <1296732551-10235-1-git-send-email-avagin@openvz.org>

On Thu, Feb 03, 2011 at 02:29:11PM +0300, Andrey Vagin wrote:
> d_alloc_name return NULL in case error, but we expect errno in
> devpts_pty_new.
> 
> http://bugzilla.openvz.org/show_bug.cgi?id=1758
> 
> Signed-off-by: Andrey Vagin <avagin@openvz.org>
> ---
>  fs/devpts/inode.c |    2 +-

Nice, but I'm not the devpts maintainer, why not send this to the vfs
maintainer instead?

thanks,

greg k-h

  reply	other threads:[~2011-02-03 15:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03 11:29 Andrey Vagin
2011-02-03 15:56 ` Greg KH [this message]
2011-02-03 16:07 Andrey Vagin
2011-02-03 19:46 ` avagin

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=20110203155612.GA983@suse.de \
    --to=gregkh@suse.de \
    --cc=avagin@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH] fs: Correctly check d_alloc_name() return code in devpts_pty_new' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).