From: Dmitry Vyukov via Linux-kernel-mentees <linux-kernel-mentees@lists.linuxfoundation.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
linux-kernel-mentees@lists.linuxfoundation.org,
Fox Chen <foxhlchen@gmail.com>
Subject: Re: [Linux-kernel-mentees] KASAN: slab-out-of-bounds Read in squashfs_get_id
Date: Wed, 14 Oct 2020 11:36:30 +0200 [thread overview]
Message-ID: <CACT4Y+aYPRvpOTubV6xL3sCoU=ukpd9Bv6yJdL7wzd=JjQfhPA@mail.gmail.com> (raw)
In-Reply-To: <CAKXUXMzFB4RVyYq0XS_1PZWgJVAW+CG8krHQr2iPAPaOykzyGA@mail.gmail.com>
On Wed, Oct 14, 2020 at 11:28 AM Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
>
> On Wed, Oct 14, 2020 at 11:21 AM Dmitry Vyukov via
> Linux-kernel-mentees <linux-kernel-mentees@lists.linuxfoundation.org>
> wrote:
> >
> > On Wed, Oct 14, 2020 at 11:13 AM Fox Chen <foxhlchen@gmail.com> wrote:
> > > > Oh, from groups. Yes, that won't work for the kernel. That also
> > > > generated an HTML email, which is generally not welcome on kernel
> > > > mailing lists.
> > > >
> > >
> > > Got it! thank you!
> > >
> > > If I miss the original email, without using "groups", how can I reply
> > > to the thread??
> > > Apart from manually copying/pasting the content, recipients, and
> > > setting in-reply-to, Is there any convenient way??
> >
> > No, unfortunately, no convenient way. Nature of email-based
> > development workflow.
> >
> > I think I've seen some web archives in the past that allowed you to
> > forward an email to yourself, and then you can reply to it normally.
> > But I don't remember where it was. Maybe you can find it.
> >
>
> If the mailing list is archived on lore.kernel.org
> (https://lore.kernel.org/lists.html), you can search the email there
> and you will find a suitable mailto link (which might work for your
> client)
>
> Alternatively, you can download an mbox, load that with an email
> client, and then respond from mutt, pine etc.
>
> syzkaller-bugs is not archived at lore.kernel.org, but I assumed all
> those emails there also go out to lkml.
>
> If useful, we could ask to archive syzkaller-bugs on lore.kernel.org as well.
All syzbot emails are also CCed to LKML, so searching linux-kernel should do.
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-10-14 9:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000002954fa05b02468d7@google.com>
[not found] ` <300c32a1-a0de-4f05-b467-0822b3d21733n@googlegroups.com>
2020-10-14 7:57 ` [Linux-kernel-mentees] KASAN: slab-out-of-bounds Read in squashfs_get_id Dmitry Vyukov via Linux-kernel-mentees
2020-10-14 8:02 ` Fox Chen
2020-10-14 8:27 ` Dmitry Vyukov via Linux-kernel-mentees
2020-10-14 9:13 ` Fox Chen
2020-10-14 9:21 ` Dmitry Vyukov via Linux-kernel-mentees
2020-10-14 9:24 ` Fox Chen
2020-10-14 9:28 ` Lukas Bulwahn
2020-10-14 9:33 ` Fox Chen
2020-10-14 9:36 ` Dmitry Vyukov via Linux-kernel-mentees [this message]
2020-10-14 9:53 ` Greg KH
2020-10-14 12:51 ` Fox Chen
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='CACT4Y+aYPRvpOTubV6xL3sCoU=ukpd9Bv6yJdL7wzd=JjQfhPA@mail.gmail.com' \
--to=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=dvyukov@google.com \
--cc=foxhlchen@gmail.com \
--cc=lukas.bulwahn@gmail.com \
--cc=syzkaller-bugs@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 NNTP newsgroup(s).