Re: in_compat_syscall() returns from kernel thread for X86_32.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: in_compat_syscall() returns from kernel thread for X86_32.
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
- Date: Thu, 18 Oct 2018 03:49:43 +0100
- Cc: NeilBrown <neilb@xxxxxxxx>, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, Dmitry Safonov <dsafonov@xxxxxxxxxxxxx>, Andrew Lutomirski <luto@xxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Denys Vlasenko <dvlasenk@xxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Borislav Petkov <bp@xxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, Brian Gerst <brgerst@xxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, linux-tip-commits@xxxxxxxxxxxxxxx, jsimmons@xxxxxxxxxxxxx
- In-reply-to: <CALCETrXB8PE4Ue0BeD0wUS9psLLjpv_pt+nj=SEaj+Nb_dZzUA@mail.gmail.com>
- References: <1460987025-30360-1-git-send-email-dsafonov@virtuozzo.com> <tip-abfb9498ee1327f534df92a7ecaea81a85913bae@git.kernel.org> <87h8hkc9fd.fsf@notabene.neil.brown.name> <CALCETrXB8PE4Ue0BeD0wUS9psLLjpv_pt+nj=SEaj+Nb_dZzUA@mail.gmail.com>
- User-agent: Mutt/1.9.1 (2017-09-22)
On Wed, Oct 17, 2018 at 07:37:42PM -0700, Andy Lutomirski wrote:
> I could get on board with:
>
> ({WARN_ON_ONCE(current->flags & PF_KTHREAD); true})
>
> The point of these accessors is to be used *in a syscall*.
>
> What on Earth is Lustre doing that makes it have this problem?
Plays with timestamps from a kernel thread, perhaps?
See the old .su joke about adenoidectomy with rectal access
for possible reasons for doing it that way...
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]