From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Amir Goldstein <amir73il@gmail.com>,
Leo Stone <leocstone@gmail.com>,
syzbot+d9efec94dcbfa0de1c07@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org, linux-unionfs@vger.kernel.org,
miklos@szeredi.hu, syzkaller-bugs@googlegroups.com,
skhan@linuxfoundation.org, anupnewsmail@gmail.com,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [syzbot] [overlayfs?] general protection fault in ovl_llseek
Date: Fri, 27 Sep 2024 21:15:22 +0100 [thread overview]
Message-ID: <20240927201522.GW3550746@ZenIV> (raw)
In-Reply-To: <CAHk-=wikugk2soi_2OFz1k27qjjYMQ140ZXWeOh8_9iSxpr=PQ@mail.gmail.com>
On Fri, Sep 27, 2024 at 12:47:16PM -0700, Linus Torvalds wrote:
> But I still strongly suspect that to make it more likely that I don't
> miss anything, you make the subject line some big clue-bat to my head
> like having "[PATCH-for-linus]" header.
BTW, what do you prefer for "please run this script with this explanation
just before -rc1" kind of stuff?
Example: https://lore.kernel.org/all/20240927015611.GT3550746@ZenIV/
I've used "[tree-wide]" as a prefix, but I've no idea what your preferences
would be in that respect...
next prev parent reply other threads:[~2024-09-27 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 7:10 [syzbot] [overlayfs?] general protection fault in ovl_llseek Leo Stone
2024-09-27 7:37 ` syzbot
2024-09-27 12:03 ` Amir Goldstein
2024-09-27 12:41 ` Amir Goldstein
2024-09-27 19:47 ` Linus Torvalds
2024-09-27 20:15 ` Al Viro [this message]
2024-09-27 20:20 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2024-09-26 17:02 syzbot
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=20240927201522.GW3550746@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=amir73il@gmail.com \
--cc=anupnewsmail@gmail.com \
--cc=brauner@kernel.org \
--cc=leocstone@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+d9efec94dcbfa0de1c07@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.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 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.