[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHk-=wjBApKY+1s7F7AB0ZnKs=SSG8jv2LMtay_MY-ym+oEKUg@mail.gmail.com>
Date: Fri, 27 Sep 2024 13:20:37 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Amir Goldstein <amir73il@...il.com>, Leo Stone <leocstone@...il.com>,
syzbot+d9efec94dcbfa0de1c07@...kaller.appspotmail.com,
linux-kernel@...r.kernel.org, linux-unionfs@...r.kernel.org,
miklos@...redi.hu, syzkaller-bugs@...glegroups.com, skhan@...uxfoundation.org,
anupnewsmail@...il.com, Christian Brauner <brauner@...nel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [syzbot] [overlayfs?] general protection fault in ovl_llseek
On Fri, 27 Sept 2024 at 13:15, Al Viro <viro@...iv.linux.org.uk> wrote:
>
> BTW, what do you prefer for "please run this script with this explanation
> just before -rc1" kind of stuff?
Well, I didn't miss that one either (see commit cb787f4ac0c2:
"[tree-wide] finally take no_llseek out") but yes, it's probably
better to mark those kinds of things very obviously too (and a
'[PATCH-for-linus]' like subject line is probably good there too).
And hey, people will forget, and I'll - mostly - figure it out anyway,
so it's not like this is a big worry. Maybe if you notice that I
missed something, you can make sure that the re-send has a big neon
sign for me.
Linus
Powered by blists - more mailing lists