All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: fix a null pointer derefrence in ocfs2_block_group_clear_bits()
Date: Thu, 12 Mar 2020 10:01:51 +0800	[thread overview]
Message-ID: <c073296c-ac3b-6e56-0786-5dac16cc1feb@linux.alibaba.com> (raw)
In-Reply-To: <20200311184031.a850f8e3dbd664b599654303@linux-foundation.org>

Hi Andrew,

On 2020/3/12 09:40, Andrew Morton wrote:

<snip>

> 
> (top-posting repaired)
> 
>> ping ?
>> cc Andrew Morton
> 
> There's something dreadfully wrong with the ocfs2-devel mailing list. 
> I almost never receive patches when people add me to cc.  I've never
> seen much of a pattern to it - it just drops stuff everywhere.
> 
> Who is the admin for this list?  Can we please move it to kernel.org?
> 

From the web page info, it was run by Srinivas Eeda, but I am not sure
whether he still maintains the list now.
So current workaround may be, sending to you directly along with cc to
the mail list.

Thanks,
Joseph

> Regarding this patch, I did actually receive one email from the server.
> From Joseph:
> 
> : > +		if (!undo_bg)
> : > +			mlog(ML_NOTICE, "%s: group descriptor # %llu (device %s) journal "
> : > +					"b_committed_data had been cleared.\n",
> : > +					OCFS2_SB(alloc_inode->i_sb)->uuid_str,
> : > +					(unsigned long long)le64_to_cpu(bg->bg_blkno),
> : > +					alloc_inode->i_sb->s_id);
> : 
> : Seems a kind of workaround.
> : I am worrying about other abnormal cases of NULL b_committed_data, it
> : may lead to a corrupt filesystem.
> : So how about isolating the journal abort case?
> 

  reply	other threads:[~2020-03-12  2:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1d38573d-61c7-be60-334e-c263caf7465c@huawei.com>
     [not found] ` <c56390f0-9f01-cd71-0b8e-b83d746bab74@huawei.com>
2020-03-09  8:26   ` [Ocfs2-devel] [PATCH] ocfs2: fix a null pointer derefrence in ocfs2_block_group_clear_bits() lishan
2020-03-10 13:07     ` lishan
2020-03-12  1:40       ` Andrew Morton
2020-03-12  2:01         ` Joseph Qi [this message]
2020-03-11  1:15     ` Joseph Qi
2020-03-12  2:38       ` lishan
2020-03-12  2:38         ` [Ocfs2-devel] " lishan
2020-03-13  8:15         ` lishan
2020-03-13  8:15           ` [Ocfs2-devel] " lishan
2020-03-19  9:26         ` Jan Kara
2020-03-19  9:26           ` [Ocfs2-devel] " Jan Kara

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=c073296c-ac3b-6e56-0786-5dac16cc1feb@linux.alibaba.com \
    --to=joseph.qi@linux.alibaba.com \
    --cc=ocfs2-devel@oss.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.