public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Dave Chinner <dchinner@redhat.com>,
	Brian Foster <bfoster@redhat.com>,
	linux-xfs@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 4.19 069/237] xfs: fix use-after-free race in xfs_buf_rele
Date: Sun, 17 Nov 2019 09:19:50 -0500	[thread overview]
Message-ID: <20191117141950.GF2261@sasha-vm> (raw)
In-Reply-To: <20191116215423.GG25427@dread.disaster.area>

On Sun, Nov 17, 2019 at 08:54:23AM +1100, Dave Chinner wrote:
>[cc linux-xfs@vger.kernel.org]
>
>Hi Sasha,
>
>Any reason these these autosel patches are not being cc'd to the XFS
>list for XFS maintainer visibility and review?

Interesting! It looks like the XFS entry in MAINTAINERS has duplicate
entries for the mailing list, once with the M: tag and once with the L:
tag, so when I run get_maintainer.pl I see:

$ scripts/get_maintainer.pl -f fs/xfs/
"Darrick J. Wong" <darrick.wong@oracle.com> (supporter:XFS FILESYSTEM)
linux-xfs@vger.kernel.org (supporter:XFS FILESYSTEM)
linux-kernel@vger.kernel.org (open list)

Which doesn't list an "open list" besides LKML.

I've fixed up my scripts to address that, sorry for missing it.

-- 
Thanks,
Sasha

      reply	other threads:[~2019-11-17 14:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191116154113.7417-1-sashal@kernel.org>
     [not found] ` <20191116154113.7417-69-sashal@kernel.org>
2019-11-16 21:54   ` [PATCH AUTOSEL 4.19 069/237] xfs: fix use-after-free race in xfs_buf_rele Dave Chinner
2019-11-17 14:19     ` Sasha Levin [this message]

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=20191117141950.GF2261@sasha-vm \
    --to=sashal@kernel.org \
    --cc=bfoster@redhat.com \
    --cc=david@fromorbit.com \
    --cc=dchinner@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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