linux-kernel - Re: [PATCH RESEND] ocfs2: use retval instead of status for checking error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20150502211319.0d406048.akpm@linux-foundation.org>
Date:	Sat, 2 May 2015 21:13:19 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	DaeSeok Youn <daeseok.youn@...il.com>
Cc:	"ocfs2-devel@....oracle.com" <ocfs2-devel@....oracle.com>,
	mfasheh@...e.com, linux-kernel <linux-kernel@...r.kernel.org>,
	Richard Weinberger <richard@....at>,
	Joseph Qi <joseph.qi@...wei.com>
Subject: Re: [PATCH RESEND] ocfs2: use retval instead of status for checking
 error

On Sun, 3 May 2015 12:02:39 +0900 DaeSeok Youn <daeseok.youn@...il.com> wrote:

> 2015-04-24 10:45 GMT+09:00 Daeseok Youn <daeseok.youn@...il.com>:
> > The use of 'status' in __ocfs2_add_entry() can return wrong
> > value. Some functions' return value in __ocfs2_add_entry(),
> > i.e ocfs2_journal_access_di() is saved to 'status'.
> > But 'status' is not used in 'bail' label for returning result
> > of __ocfs2_add_entry().
> >
> > So use retval instead of status.
> >
> > Reviewed-by: Joseph Qi <joseph.qi@...wei.com>
> > Signed-off-by: Daeseok Youn <daeseok.youn@...il.com>
> > ---
> Andrew.
> 
> How is it going this patch, please check for me.

I merged this over a week ago and it is in linux-next:
http://ozlabs.org/~akpm/mmotm/broken-out/ocfs2-use-retval-instead-of-status-for-checking-error.patch

You were sent a commit email at the time.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/