mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr>
Cc: Phillip Lougher <phillip@squashfs.org.uk>,
	linux-kernel@vger.kernel.org, hsinyi@chromium.org,
	regressions@leemhuis.info, regressions@lists.linux.dev,
	dimitri.ledkov@canonical.com, michael.vogt@canonical.com,
	phillip.lougher@gmail.com, ogra@ubuntu.com,
	olivier.tilloy@canonical.com,
	Marc Miltenberger <marcmiltenberger@gmail.com>
Subject: Re: [0/3] squashfs: fix some regressions introduced in the readahead code
Date: Sat, 22 Oct 2022 15:56:27 -0700	[thread overview]
Message-ID: <20221022155627.be13b4ea9769f76818e73f81@linux-foundation.org> (raw)
In-Reply-To: <4493e774-ff23-e2a1-4aa7-28b190eb909d@alu.unizg.hr>

On Sat, 22 Oct 2022 03:38:01 +0200 Mirsad Goran Todorovac <mirsad.todorovac@alu.unizg.hr> wrote:

> Please consider crediting Marc Miltenberger, who was first to reproduce 
> and confirm that the
> bug was not in my build but in mainline kernel.

Thanks, Marc.  I've added your Reported-by: to my copies of the
three patches.

      parent reply	other threads:[~2022-10-22 22:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 22:36 Phillip Lougher
2022-10-20 22:36 ` [PATCH 1/3] squashfs: fix read regression introduced in " Phillip Lougher
2022-10-20 22:36 ` [PATCH 2/3] squashfs: fix extending readahead beyond end of file Phillip Lougher
2022-10-20 22:36 ` [PATCH 3/3] squashfs: fix buffer release race condition in readahead code Phillip Lougher
2022-10-21 12:42 ` [0/3] squashfs: fix some regressions introduced in the " Bagas Sanjaya
     [not found] ` <4493e774-ff23-e2a1-4aa7-28b190eb909d@alu.unizg.hr>
2022-10-22 22:56   ` Andrew Morton [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=20221022155627.be13b4ea9769f76818e73f81@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dimitri.ledkov@canonical.com \
    --cc=hsinyi@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcmiltenberger@gmail.com \
    --cc=michael.vogt@canonical.com \
    --cc=mirsad.todorovac@alu.unizg.hr \
    --cc=ogra@ubuntu.com \
    --cc=olivier.tilloy@canonical.com \
    --cc=phillip.lougher@gmail.com \
    --cc=phillip@squashfs.org.uk \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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
all inboxes | Powered by JetHome®