From: Luis Henriques <luis.henriques@canonical.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Bret Towe <magnade@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ocfs2-devel@oss.oracle.com, mfasheh@suse.com, jlbec@evilplan.org,
Sunil Mushran <sunil.mushran@oracle.com>
Subject: Re: BUG in ofcs2_change_file_space
Date: Wed, 20 Jun 2012 23:29:10 +0100 [thread overview]
Message-ID: <87pq8tk47d.fsf@canonical.com> (raw)
In-Reply-To: <20120620145659.a5fff5f6.akpm@linux-foundation.org> (Andrew Morton's message of "Wed, 20 Jun 2012 14:56:59 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
> On Wed, 20 Jun 2012 19:01:30 +0100
> Luis Henriques <luis.henriques@canonical.com> wrote:
>
>> >> a patch has been available for this for a while now
>> >> found here: http://oss.oracle.com/pipermail/ocfs2-devel/2012-January/008464.html
>> >> but it still has not hit mainline
>> >> is there any way we can get this included?
>>
>> I believe something like this would be more appropriated, as a NULL as the
>> 'file' parameter seems to be valid in that context:
>>
>> ---
>> fs/ocfs2/file.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/ocfs2/file.c b/fs/ocfs2/file.c
>> index 6e39668..84822a4 100644
>> --- a/fs/ocfs2/file.c
>> +++ b/fs/ocfs2/file.c
>> @@ -1950,7 +1950,7 @@ static int __ocfs2_change_file_space(struct file *file, struct inode *inode,
>> if (ret < 0)
>> mlog_errno(ret);
>>
>> - if (file->f_flags & O_SYNC)
>> + if (file && (file->f_flags & O_SYNC))
>> handle->h_sync = 1;
>>
>> ocfs2_commit_trans(osb, handle);
>
> Sunil, does this look OK to you? And Bret, can you please test it?
>
> Luis, can you please prepare a proper, signed-off, changelogged version
> of this and I'll grab it, thanks.
>
Sure, I'll send it in a minute.
Cheers,
--
Luis
>
>
> I'm not seeing any OCFS2 activity in mainline from Joel and Mark in six
> months, so I'm getting those i-have-a-new-subsystem-to-maintain
> feelings.
>
> If anyone else has any urgent OCFS2 patches then please resend them, cc
> myself and cc linux-kernel.
next prev parent reply other threads:[~2012-06-20 22:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 22:23 BUG in ofcs2_change_file_space Bret Towe
2012-05-22 3:11 ` Bret Towe
2012-06-20 17:38 ` Bret Towe
2012-06-20 18:01 ` Luis Henriques
2012-06-20 21:56 ` Andrew Morton
2012-06-20 22:29 ` Luis Henriques [this message]
2012-06-20 22:34 ` [PATCH] ocfs2: Fix NULL pointer dereferrence in __ocfs2_change_file_space Luis Henriques
2012-06-20 22:39 ` Luis Henriques
2012-06-20 22:42 ` Andrew Morton
2012-06-20 23:18 ` Mark Fasheh
2012-06-21 6:12 ` Joel Becker
2012-06-21 4:39 ` Bret Towe
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=87pq8tk47d.fsf@canonical.com \
--to=luis.henriques@canonical.com \
--cc=akpm@linux-foundation.org \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnade@gmail.com \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=sunil.mushran@oracle.com \
/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