Linux-XFS Archive mirror
 help / color / mirror / Atom feed
From: Marius Fleischer <fleischermarius@gmail.com>
To: Leah Rumancik <leah.rumancik@gmail.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
	Dave Chinner <david@fromorbit.com>,
	linux-xfs@vger.kernel.org,  linux-kernel@vger.kernel.org,
	harrisonmichaelgreen@gmail.com,  syzkaller@googlegroups.com
Subject: Re: KASAN: null-ptr-deref Write in xlog_cil_commit
Date: Thu, 25 Apr 2024 13:33:51 -0700	[thread overview]
Message-ID: <CAJg=8jw=D5kVL6ETwm5EMias4rgUKfEg2H9dLUgesqf1wq7evw@mail.gmail.com> (raw)
In-Reply-To: <CACzhbgSdDBzTyqc3ci17U2DG8GKo=Fq=H3c+eTM7J5u_Xh2QmA@mail.gmail.com>

Hi Leah,

Thanks for your response!

I can reliably reproduce the issue, so I'll try to create a patch and
let you know.

Wishing you a lovely day!

Best,
Marius

On Thu, 25 Apr 2024 at 13:31, Leah Rumancik <leah.rumancik@gmail.com> wrote:
>
> Hi Marius,
>
> Thanks for the bug report. If you can reliably reproduce this issue
> and can provide a patch which fixes it, I can add that patch to the
> next set of 5.15 backports. I am a bit limited for time at the moment
> though and trying to work on the backlog of backports into 6.1.y as
> well, so I am not sure what the exact timeline would look for a 5.15.y
> set yet.
>
> - Leah
>
>
> On Tue, Apr 23, 2024 at 8:42 PM Darrick J. Wong <djwong@kernel.org> wrote:
> >
> > On Tue, Apr 23, 2024 at 08:05:22AM -0700, Marius Fleischer wrote:
> > > Hi Dave,
> > >
> > > Thank you so much for your detailed explanations!
> > >
> > > > > Do you think it would make sense to backport that patch to 5.15.156 (the
> > > > > LTS kernel)?
> > > >
> > > > That's up to the 5.15 LTS maintainers to decide. They also need to
> > > > weigh up the fact that xlog_cil_kvmalloc() doesn't exist anymore in
> > > > the upstream code base. i.e. we found other places that had the same
> > > > kvmalloc() performance problems, and so lifted that code up further
> > > > and used it in other places in XFS....
> > > >
> > >
> > > Understood. Please allow me one last follow-up question. Did I add the correct
> > > maintainers/mailing lists to reach the 5.15 LTS maintainers? If not,
> > > how do I find
> > > the correct addresses? I used scripts/get_maintainer.pl as suggested here
> > > (https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html)
> > > to locate maintainers/mailing lists.
> >
> > You got it correct -- Leah is the 5.15 maintainer of record.
> >
> > --D
> >
> > > Wishing you a lovely week!
> > >
> > > Best,
> > > Marius

      reply	other threads:[~2024-04-25 20:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 18:03 KASAN: null-ptr-deref Write in xlog_cil_commit Marius Fleischer
2024-04-18 22:02 ` Dave Chinner
     [not found]   ` <CAJg=8jycPX=fQskUb=48g=AS7-uUNAVKZyZ+tyAC5uGYwfpabg@mail.gmail.com>
2024-04-21 23:48     ` Dave Chinner
2024-04-23 15:05       ` Marius Fleischer
2024-04-24  3:42         ` Darrick J. Wong
2024-04-25 20:31           ` Leah Rumancik
2024-04-25 20:33             ` Marius Fleischer [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='CAJg=8jw=D5kVL6ETwm5EMias4rgUKfEg2H9dLUgesqf1wq7evw@mail.gmail.com' \
    --to=fleischermarius@gmail.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=harrisonmichaelgreen@gmail.com \
    --cc=leah.rumancik@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=syzkaller@googlegroups.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).